Refactor/hexagonal pattern poc v2

[Dan-Y-Ko]

hexagonal architecture updated

some notes:

I first changed it to follow this folder structure

application
domain
infrastructure

couple reasons why I didn't like this

• It felt too much like layers to me. Hexagonal architecture in implementation is actually quite similar (if not the same) as n-tier architecture. After a lot of reading, it seems the main difference is conceptually. Instead of data flowing down in layers, the ports and adapters is emphasized. I won't talk more about this as I'm sure you already know.
• With the concept of primary and secondary ports/adapters I found so many conflicting info about what goes where so that's why I decided to refactor again
• It became very confusing to me and hard to keep track of the different ports/adapters when it was separated by "layers"

so the change is what I like better

application
ports
adapters

One other issue I came into was properly implementing the primary port (the primary adapter). Ideally it'd be the service acting as the adapter but first problem is we can't use classes in next with server component / actions. The second issue was that I couldn't really get the transformation to work while also keeping the interface in the port intact. The only solution I could think of is to return the normal response (instead of async response) from the adapter / service and add another layer to do the response transformation but Idk if there's much benefit to this. Instead I just decided to have the usecase implement the port, which I don't think 100% aligns with the architecture but I think it's fine, given the restraints with the tech stack.

I couldn't get the tsyringe resolve to work in the component so I instantiated the classes manually.

btw, I didn't go over the changes in depth because I figured you'd know this already but if you need to me to go over it, I can

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
chingu-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 4, 2024 3:54am

[Dan-Y-Ko]

so one issue I saw. The cache and token isn't being enforced here. I am pushing a "solution" but it's not great because it's fragile. However, I'm not sure what else could be done....would be possible if classes were useable. But that also comes with an issue of adding more code