Building applications with APIs
Development teams often ask me, "How should we structure our application?" While the answer is never simple, it often involves a statement recommending to build an API, between your presentation
Here is the full post
https://blog.hyper63.com/apis/
Regardless of architecture, I think it is always good practice to isolate your business logic from your general services and a frameworks.
As a developer, what do you think?
Trending on Indie Hackers
Hey, I enjoyed reading your post and the pattern you are describing is something I’ve used for quite some time, and can attest that keeping business logic in one place (whatever you call it), is a must if you want to be able to make predictable changes to your business logic. I even end up use this approach when building a “monolith” because it just makes the development experience so much better.
Hey Fredrik,
That’s great, yes, whether micro service or monolith, this pattern will work, have you implemented ports and adapters pattern and inverted the control so all implementation details depend on your business logic/rules?
It so cool that you are using this pattern on many projects unfortunately many teams do not, and end up in a big ball of mud.
Thank you for reading and sharing your experience.