4 ms·
Splitting the workloads is a good, natural progression. The next pain point will be data boundaries. What tables are shared and joined against in different area
by sethammons 4y ago
Splitting the workloads is a good, natural progression. The next pain point will be data boundaries. What tables are shared and joined against in different areas of the code? The ability to scale data access can be hard. As teams grow, shared understanding goes down and eventually data will get tangled together. Scaling systems is scaling data access. Scans, joins and aggregations will put pressure on the db and moving segments of data to their own data stores will be called for. Will you be able to untangle the monolith?
- jbverschoor 4y agoDoesn’t mean microservices is a good fit. You’ll need a team per serviceC but you don’t have the people who know the boundaries. Better keep it as a monolith in that case. It’s far far far worse to split something up with bad understanding about the data and access patterns than to just struggle along.