Building a new project
.
.
.
Must
.
.
.
Resist
.
.
.
This Urge
.
.
.
To
.
.
.
Use
.
.
.
Micro services

Why ? just prepare the operation phase before starting dev and it all be good . Docker helps me a lot .Good Luck !

@skonteam even from an ops point of view, isn't it straightforward to just have a monolithic application with a single storage backend? At least when creating an app from scratch with tight RTM timelines and limited resources, I can rest (no pun intended) assured that I can scale out my stateless web servers and scale up my db servers without a lot of fuss. As opposed to say a microservices architecture where I need to figure out the granularity of each service, how best to orchestrate them, an extra aggregation layer to code up, not to mention that security also gets slightly complicated. And then comes docker - it is pretty cool and has its use cases and I can see how it can really shine when applied to microservices but that is only the ops part of microservices - but it does not come without its complications.

I'm not dissing microservices or docker... Just saying that in my case, I'd like to focus on getting the app out without suffering from the epidemic that seems to have gripped our industry - 'microservices envy'. And if my app survives long enough to warrant a move to microservices, nothing like it.

Microservice is just hardcore encapsulation riding a hype. Stick to SOLID and move your services as your project grows. Avoid too much "common" libs. Create a context map to help you keep track of your isolations.