3 ms·
> There are good reasons to use microservices, like when you have 100+ engineers Its enough to have 2 that work in different domains with different constraints
by fiedzia 7y ago
> There are good reasons to use microservices, like when you have 100+ engineers
Its enough to have 2 that work in different domains with different constraints and different tools. Company scale is completely irrelevant here.
> But if you are a normal company, you will probably never have enough engineers to make microservices worthwhile in the first place
Many "normal" companies use microservices and common reason is that they simply cannot function otherwise.
> But for most small to medium companies, a planned 5 minute downtime in the middle of the night is completely no problem,
The fact that some site doesn't function for 5 minutes may not be a problem, the fact that any change requires many people agreeing on deployment time often is.
- jdc 7y agoIts enough to have 2 that work in different domains with different constraints and different tools. Wouldn't that be more or less be just two monoliths?
- fiedzia 7y agoIf they both work for the same organization to achieve common goal, communicate through some interface they agree on, having to coordinate occasional changes that affect both codebases, than no. If they are completely isolated, than yes, but its really rare scenario. A common example would be a website that gathers/presents some data from users, and a service that provides analytics of said data. Both domains may require completely different technologies.