But if your project is still small, with a small team you likely don't need that... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

slashdev on July 9, 2015 | parent | context | favorite | on: Introduction to Microservices

But if your project is still small, with a small team you likely don't need that yet. However, if your going to start with a monolith with the intent of going to microservices you had better have strong architectural discipline in the team. Otherwise, with no physical barrier to prevent it, developers are going to fall prey to the temptation of taking shortcuts and reaching across module boundaries, out making chatty APIs that can't be made distributed in a practical manner.

jedberg on July 9, 2015 [–]

Even with a small project and small team, it's nice to be able to scale up just the part that is overloaded. Especially if you're on a small budget.

And I was working on the premise that you are already doing microservices, so presumably you are already taking the overhead hit.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact