2 ms·
Probably keep it as a monolith. You don't need to define rigid ownership. Though some pieces will move slower than others (and some things will never change),
by echelon 7y ago
Probably keep it as a monolith.
You don't need to define rigid ownership.
Though some pieces will move slower than others (and some things will never change), a single deploy cadence is probably fine.
There's also the danger of an incomplete microservice migration where you've now got hobbled together half-service weirdware that you have to support forever.
Don't do microservices until engineers working on their thing break your thing.
- Sean1708 7y ago> an incomplete microservice migration where you've now got hobbled together half-service weirdware that you have to support forever. Ugh I have to deal with this at my current job, except it's not an incomplete microservice migration it's by design and comes with a weird hobbled-together event queue implemented as a table in the DB and that has a known race condition that pops up every couple of weeks.