3 ms·

I'm curious what makes you think that. At the end his bio says he has 12 years of experience, and from his blog seems to know a thing or two.

• gjolund 10y ago
  Because scaling a monolith is not a realistic approach. Every single monolith I have worked on has been refactored as domain specific microservices, and in every case it was a resounding success.
  • eric_h 10y ago
    In my experience scaling a monolith just costs more (i.e. hosting costs). Our product, when we started, was quite expensive to run at our high traffic times, but we were eventually able to cut our costs drastically by breaking certain pieces out into services.
    • gjolund 10y ago
      Depends on the product, but for many startups those additional costs can be crippling. Also, I have found it much easier to onboard a new engineer, give them the requirements for a service and let them go at it. I've been using AWS Lambdas to great effect in this way.
      • eric_h 10y ago
        Certainly, not everything is a nail.
  • collyw 10y ago
    "I've never implemented monolith properly, so you should avoid them."