Don't miss any new articles and instead receive them in your inbox as soon as they become available.
We have experience with both — do microservices only when you have dedicated teams for each of them, and they have a clear separation of data, responsibilities, and stacks.
Otherwise, you can end up with a completely scrambled architecture and where everything is 10x more complex and difficult than needed!
Are you starting and your product is about to change a lot? Embrace the monolith. It’s great architecture when one needs to iterate quickly and keeps a disciplined mindset, with many benefits. Just make sure your architecture is efficient and easy to understand.
This is a question asked during an AMA (Ask Me Anything) session — follow the blog to keep up with the common engineering questions and answers, or join our free mentoring platform!