3 ms·
If you can't roll a service out independent of some other process, you don't have a service based architecture, you have an even worse monolith. You are blamin
by kasey_junk 11y ago
If you can't roll a service out independent of some other process, you don't have a service based architecture, you have an even worse monolith. You are blaming other people for problems, you yourself (or your team) are introducing.
Pulling out the code is not what is important typically in these sorts of migrations, what is important are:
1 - getting product definition about when/where you can loosen your consistency constraints on your data.
2 - building specified protocols between components that can support backwards/forwards compatibility.
If you continue to need strong consistency and can't support backwards/forwards schema changes in your shared data, you cannot build a service based system and would be better off improving your monolith.
PS: There isn't anything wrong with monolithic designs (cause that word doesn't really mean anything) for a huge swath of the technical world. If your team wasn't able to develop a good monolith it is incredibly unlikely they will be able to develop a good service based system.