Should that be a microservice? Factors to keep in mind

Re:Should that be a microservice? Factors to keep in mind by threeseed on Saturday April 20, 2019 @08:35PM (#19709807)

It really is trivial to automate the process of creating a new service with a corresponding repo and CI pipeline. And with tools like giter8 it's not that hard to standardise on service layout and components as well. You could easily do it in a few hours.

Likewise just using modules looks good on paper but in practice most languages make it too easy to reference code in other modules. And so very quickly you end up with spaghetti code. So regardless of whether you use modules or services you still need to do a lot of upfront work in setting and enforcing some design/architectural rules.

[ Parent | on HN ]

Re:Should that be a microservice? Factors to keep in mind by clintonb on Saturday April 20, 2019 @09:51PM (#19710084)

Agreed. We built cookiecutter templates at edX for the basic Django service and Ansible playbook. We built shared libraries for OAuth and other shared functionality.

That said, much of this did not come into place until we were on the third microservice. Starting with templates and libraries for the very first service would have definitely been premature optimization, and have resulted in wasted time and later rework.

[ Parent | on HN ]

Re:Should that be a microservice? Factors to keep in mind by discreteevent on Sunday April 21, 2019 @02:58AM (#19710885)

It's just as easy to create spaghetti with microservices. Circular dependencies all over the place. Discipline is discipline no matter what you use. Microservices just make lack of discipline harder to fix.

[ Parent | on HN ]