Hacker News new | past | comments | ask | show | jobs | submit login

You would never start out building a website with microservices. They have all the downsides people have already commented on.

But are people taking into consideration team/employee size?

If you have 100+ engineers working on a site, in different countries with different managers and different leaders with different product goals. Then the microservice architecture becomes a necessary evil.




In my experience I’ve seen good productivity out of a monolithic architecture up to 50 developers. Have others seen the monolithic architecture scale higher?


Google?


They have a monorepo - not monolithic app.


I think the expectation is that the app is relatively monolithic, as well. If you can force everyone into a single repository, why not force them to a single architecture to push data in?


If the current gmail is any indicator, have they really succeeded?

Otherwise, I'm guessing they don't actually have that many pages with everyone working on them.




Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: