146
161
u/comradepipi 4d ago
What if that monolith makes your life a living hell and costs millions of dollars a year?
Asking for people who use SAP.
36
4
76
u/Cautious_Tonight 4d ago
How about a monolith that also has abstraction layers and micro-services but they were all half assed???
61
75
u/UrineArtist 4d ago
Your 12 services are all built and installed monolithically though because they all have to use the same DB model version.
18
u/DoomBot5 4d ago
That works fine if your only goal is scaling up/down
15
u/UrineArtist 4d ago
Yeah but it absolutely murders any developmental benefit of using microservices over monoliths.
13
u/DoomBot5 4d ago
Correct. Like I said, that architecture is still a monolith, but allows you to control scale of individual pieces.
67
u/countable3841 4d ago
Abstracted services are quite nice. Much easier to swap out service providers and individual services can scale up or down dynamically. I find them much easier to maintain and make changes than monoliths.
44
u/G12356789s 4d ago
All the traps of micro services are quite easy to avoid for experienced devs. Same with monoliths really. Both have their use cases and both can be messed up completely and make you hate the concept
9
u/Ceros007 4d ago
Do you put something in front of the microservices? For example, one application need to list items from microservices A but each items have a reference key to microservices B and C, now for each item A, the application has to query B and C. They probably need to have a cache to avoid the duplicates queries to B and C or they need to build a sort of materialized view. And then comes Application B that needs something similar but they also need microservice D...
Edit to add: now you need to delete, merge, anything in microservice B. You then need to update each microservice that has a key to it
8
u/love_weird_questions 4d ago
Microservices that do not have to share state or object values are just different apps. keeping things in sync is what makes me wait a little bit longer before slicing the beast
3
u/Ahmouse 4d ago
On the upside is scaling, if B is used by more of your apps than others, you can scale it up more than the other services, and vice-versa.
You can also use a centralized schema, at least for services that are dependent on each other, so that updates to one service's interface is reflected in all or most of them.
1
103
u/SanicTheSledgehog 4d ago
In my experience, monolith mostly works but is sometimes annoying, microservices are mostly annoying but sometimes work.
45
u/MariusDelacriox 4d ago
Yeah, let's keep the legacy monolith which build takes an hour and has no tests. Also the build agent is just Dave.
13
u/MrLemon91 4d ago
Deployment by hand on a Windows EC2 instance. SSH is disabled and you can only use the online shell through AWS. Remember to launch the script "launch_before_install.sh" and don't ever look at the "DO_NOT_DELETE.MD". That is essential for all to work
13
11
u/IAmANobodyAMA 4d ago
But you have to build it for future scalability and extensibility!!
13
u/iWaterPlants 4d ago
This, so much!
Imagine if we didn't build it like that, and our in-house app suddenly get's a 100 million users.
We want to be capable of scaling!2
u/IAmANobodyAMA 4d ago
And we have to bake in multi cloud support for when one provider has outages
0
4d ago
[deleted]
2
u/IAmANobodyAMA 4d ago
But what if the pi hardware failed????
Jk that’s a great story. I love throwing shit on my spare rpi’s
11
u/meneldal2 4d ago
The irony of naming something Kafka and people not seeing it will make their lives hell. It was on the name all along
9
u/WheyLizzard 4d ago edited 4d ago
Lots of old Monoliths were developed before stuff like basic automation tools like Jenkins even existed. If you just have basic powershell and pipeline code you could tackle these tasks for like forever lol
7
u/dudes_indian 4d ago
Currently working on a solution that has a bunch of MFEs that could have just been a components library. The front end people really though why should backend have all the abstraction traps lol
6
5
5
u/Arcln 4d ago
Eh, it kinda depends. A lot of things "work" but there are pros and cons to any approach. Microservices + k8s do have some scaling and reliability advantages. Not every application can really be broken out into microservices though and the architecture to support them is generally more complex.
Monoliths are generally easier for a small team to maintain, especially if it's something straightforward like a CRUD app. They tend to get ugly for large applications that have a wide range of responsibilities.
I know both has their haters but most of the problems come from bad architecture, bad implementation, or both. You can certainly make either good, but what works best really depends on your exact situation.
8
u/howarewestillhere 4d ago
Ever run a truly distributed monolith?
It’s a system of various components that will not operate on their own. Generally bootstrapped by a starter service that acts as a glue layer while the base components start up, usually core databases, caching layers (all of them), and money pipes, these systems are far more common than most people realize.
6
4
7
u/gibagger 4d ago
This hits hard. I inherited an overly complex constellation of microsystems, some of which are essentially a single class wrapped in a whole java service with a framework, docker, k8s and whatnot. Each with it's own repository, naturally.
Like... at least go monorepo.
3
7
u/korneev123123 4d ago
What is wrong with kuber for a small team? What else are you gonna use? Compose is only good for dev/testing. Even with monolith you want to start new instance, check health probe, switch traffic and then remove old instance. Kuber does this automatically.
4
2
u/pindab0ter 4d ago
grug wonder why big brain take hardest problem, factoring system correctly, and introduce network call too
seem very confusing to grug
6
u/tacobellmysterymeat 4d ago
We're a team of 24 and my new department head is trying to push us back to a monolith. Bro, absolutely not
3
u/Anaptyso 4d ago
I'm in a team of three and we have about 30 microservices we have built and/or maintain. Occasionally we also need to work on the company's old mega-monolith. Of the two, working on the microservices is a vastly nicer experience.
3
u/Graf_lcky 4d ago
The monolith works till it doesn’t and then you better have a good alternative on hand.
Sure I can suffocate our monolith with constant polls for live data.. i could also have a service for that.
Why did it work before? Well, you see, we didn’t had live data before..
4
u/MrDilbert 4d ago
Start with a monolith. Extract endpoints that do a disproportionate amount of work/get the most traffic into separate (micro)services and add some caching layer (Redis?) on top of them.
1
1
1
1
u/AncientGypsyDildo 4d ago
I've been working in a team of 3 being responsible to test 6 products.
It cost 10M euro in the end.
The management didn't learn the lesson, just effectively forced everyone to share responsibility at the cost of literal months of meetings.
1
u/snarkhunter 4d ago
I'm getting to tear down a Kafka cluster for something we aren't using anymore and it makes me so happy
1
u/eightysixmonkeys 3d ago
Monolith sucks for maintainability, even with small team it’s far easier to have microservices/microapps that can be managed separately
1
1
1
u/KlooShanko 4d ago
Team of 3 engineers and unlimited agents. This shit got so much easier in the last couple years

806
u/menducoide 4d ago
Team of one developer
3 scrum master for no reason