this post was submitted on 12 May 2024
188 points (90.9% liked)

Programmer Humor

31224 readers
50 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 4 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 4 points 1 month ago (1 children)

Something to consider is a monolith can have different entry points and a focused area of work. Like my web application monolith can also have email workers, and background job processers all with different container specs and scaling but share a code base.

And coming from a background where I work heavily with Postgres a bunch of smaller segregates databases sound like a nightmare data integerity wise. Although I'm sure it can be done cleanly there are big advantages with having all your tables in one database.

[โ€“] [email protected] 2 points 1 month ago

I see, I'm definitely biased towards micro services after years of dealing with horribly made monoliths but I see what you mean.

At the end of the day I think both approaches have pros and cons.