Is N-tier architecture frowned upon?
I have some java/spring projects under my belt, most of which are N-tier architecture-based and I've been wondering if this approach is too simple? I mean do companies prefer to use Hexagon/DDD/Microservices most of the time? I'd love to hear some advice
4 Replies
⌛ This post has been reserved for your question.
Hey @IamMax420! Please useTIP: Narrow down your issue to simple and precise questions to maximize the chance that others will reply in here./closeor theClose Postbutton above when your problem is solved. Please remember to follow the help guidelines. This post will be automatically marked as dormant after 300 minutes of inactivity.
It depends on the project
I'd argue that for most projects that aren't too big, it's perfectly fine
Both have benefits and disadvantages and what option is better depends on the project, the developers, your requirements, etc
and there are also options in between
and architectural decisions are not necessarily mutually exclusive
great, thanks for your feedback
If you are finished with your post, please close it.
If you are not, please ignore this message.
Note that you will not be able to send further messages here after this post have been closed but you will be able to create new posts.
💤 Post marked as dormant
This post has been inactive for over 300 minutes, thus, it has been archived.
If your question was not answered yet, feel free to re-open this post or create a new one.
In case your post is not getting any attention, you can try to use /help ping.
Warning: abusing this will result in moderative actions taken against you.