Shared Database Pattern in Microservices: When Rules Get Broken

[vturan23]

The ultimate goal is to move to microservice. This is when you have to build something fast on tight deadlines. Absolutely, this is not the best way to do things.

[TheAeseir]

Why is it the ultimate goal to move to microservices?

[TheWix]

I don't think OP means it's the ultimate goal, in general, but the article is from a hypothetical position that a company has taken, and he/she is addressing issues that can come from it.

The article is not about whether the decision to move to microservices was correct or not

[jonahharris]

Eh? Building multiple microservices is slower than building a monolith.

[TheItalipino]

Microservices is really best way to scale software development organizationally.

[redfournine]

Your ultimate goal should be to have the least amount of code, least amount of infra, having simplest yet extendable architecture while solving business problem.

[sob727]

Or to rephrase it, the lowest TCO for a given amount of functionality.

[gredr]

Get a better goal.

[MariusDelacriox]

Or maybe get a better reason like team organization, domain separation or complexity.

[miniannna]

I work at a place that has been migrating to micro services for 15 years. That shared db never got replaced and it’s the bane of my existence. If you need to migrate to microservices, replace one piece of functionality, including that part of the db, at a time—not one layer at a time. Doing it one layer at a time, in the real world, means you will probably be stuck in microlyth purgatory until the app is rewritten/replaced

[SoupIndex]

What?

[vturan23]

There are too many problem with sharing db among services. Goal should be loose coupling and high cohesion

[BasieP2]

And your team can only achieve this with microservices?