News for hackers. Stuff that matters.
Re:Startup CTO – Premature Scaling by swsieber on Monday May 08, 2017 @09:16AM (#14291177)
This should get more emphasis.

Microservices do require more overhead. Additionally, they require you to be familiar enough with you business logic to know where you boundaries lie - changing abstraction boundaries is much harder with microservices than with a monolith.

I think that while they are great for scaling, they are a lot harder to use to successfully get off the ground (though I'm betting that there are places that have successfully done so)

Re:Startup CTO – Premature Scaling by ben_jones on Monday May 08, 2017 @09:39AM (#14291335)
You also have to know how to "do" microservices. Whether it's incorporating message queues like RabbitMQ, protocols like gRPC, etc., it's very hard to get right the first time by winging it without previous experience. Redesigning microservices after is a PITA.
Re:Startup CTO – Premature Scaling by mcginleyr1 on Monday May 08, 2017 @11:03AM (#14292098)
100% agree. Your path is based on your teams experience and capabilities, not trends.