A pattern language for microservices

Re:A pattern language for microservices by jtmarmon on Wednesday December 27, 2017 @10:58AM (#16015468)

Thanks for being so candid. I made the same mistake at my startup when given the chance to start greenfield due to a pivot. I ate my pride and switched back to a monolith after realizing I was spending more time doing devops than I was coding.

[ Parent | on HN ]

Re:A pattern language for microservices by friendly_chap on Wednesday December 27, 2017 @11:03AM (#16015498)

You are welcome. I believe you 100% made the right call. And yeah, the cost of devops is massive: you have to automate everything!

If you have a monolith or two you can easily do one off tasks manually and forget about them forever, with microservices it's all about automation.

[ Parent | on HN ]

Re:A pattern language for microservices by akulbe on Wednesday December 27, 2017 @02:09PM (#16017094)

Isn't there a sense in which automation, for the sake of creating something more predictable/repeatable/maintainable, is a good thing though?

[ Parent | on HN ]

Re:A pattern language for microservices by jtmarmon on Wednesday December 27, 2017 @04:00PM (#16017996)

predictable repeatable and maintainable are all great and important things. But micro services makes everything you do less predictable repeatable and maintainable. You must automate many more things with micro services to achieve the same level of predictable repeatable and maintainable as you have with a monolith.

There are many possible benefits of microservices, few of which outweigh the massive costs for many (dare I say most) startups.

[ Parent | on HN ]