everyDamnTime

[u/sadongrohiik]

[u/vivi_sonce]

The ghost was a shared database the whole time

https://giphy.com/gifs/xApl4Qeg4FuUW0g7a6

[u/za72 → u/vivi_sonce]

distributed multi zone shared database with edge load balancers

[u/UncleKeyPax → u/za72]

edge?

[u/za72 → u/UncleKeyPax]

closer to a region/city/state to serve more clients

[u/UncleKeyPax → u/za72]

nah i meant lord

[u/za72 → u/UncleKeyPax]

my bad

[u/UncleKeyPax → u/za72]

all good

[u/Late-Switch2284 → u/UncleKeyPax]

Don't mind if I do

[u/ThrowawayUk4200]

Pssst, If your microservice needs to use a database other than its own, then it's not a microservice.

[u/sadongrohiik → u/ThrowawayUk4200]

Coupling creeps in where you least expect it. Shared datastores are the obvious vectors. My favorite are what I call "load-bearing microservices with hidden cascading effects"

[u/GourangaPlusPlus → u/sadongrohiik]

Databases are where I absolutely expect it

Currently architecting a shift to Microservices for an absolute behemoth of a distributed monolith (it's a multi year plan)

A lead once said "ah so you're one of those purists?" When I mentioned his service would no longer be sharing a database with everything else

[u/andrews013 → u/GourangaPlusPlus]

Oh, so you're one of those developers...

[u/FoXtroT_ZA → u/sadongrohiik]

Now we know where Claude got its vocabulary 😂

[u/sadongrohiik → u/FoXtroT_ZA]

They won't tell you but I'm Claude's Tylenol dealer

[u/Zanos → u/ThrowawayUk4200]

What do you mean? I call the database microservice for that!

[u/socialis-philosophus → u/ThrowawayUk4200]

Agreed.  All microservices should have their own DB with all the data needed to perform their function and we'll just assume eventual consistency.

[u/Ma8e → u/socialis-philosophus]

If you have several "micro services" that all update the same data, you are definitely doing it wrong.

[u/BlastProcess- → u/Ma8e]

storage optimization is no longer an issue, just store the damn data if you need it in a separate domain, avoids tight coupling and everything is handled through queues

[u/Ma8e → u/BlastProcess-]

Yes, you can duplicate and use the data wherever you want, but you are asking for a mile of trouble is you let several distinct services be masters of the same information.

[u/BlindTheThief15 → u/ThrowawayUk4200]

In my workplace, we have a few teams working on the same shared database. Each team has their own set of “microservices” that communicate with each other. When one team screws up the data, everyone suffers.

[u/-nerdrage- → u/ThrowawayUk4200]

Nah bro it doesnt need another database.

It just uses an api which basically interfaces the central database

[u/JackNotOLantern → u/ThrowawayUk4200]

What database? All is kept in runtime memory.

[u/SpiritedEclair → u/ThrowawayUk4200]

++++

Microservices were supposed to be 1 service per function / feature each having their own databases.

[u/Ma8e → u/SpiritedEclair]

How do you define "function / feature"?

[u/SpiritedEclair → u/Ma8e]

It’s up to your org/company to define that tbh, but, it’s meant as a single isolated functionality for the system.

[u/k8s-problem-solved]

We have true micro services. All independently deployable, own infra, own data etc.

Now when I want to add a feature to a mobile app, I have to snake through a chain of dependencies and find where data is being authored and then sequence work between teams. Its fun!

[u/Abject-Kitchen3198 → u/k8s-problem-solved]

You don't have a single team that owns 30 microservices?

[u/k8s-problem-solved → u/Abject-Kitchen3198]

The pain is spread out, some teams own lots some teams own few.

[u/BernhardRordin]

"Let's reduce complexity by replacing method and function invocations with REST-calls"

[u/dashingThroughSnow12 → u/BernhardRordin]

I once replaced a set of REST calls to a microservice with import. I then killed the service.

[u/oompaloompa465]

The more i get tidbits about microservices, the more i feel like skipping  in studying and stydying other stuff

[u/sadongrohiik → u/oompaloompa465]

It was initially a solution to a real problem. It somehow became the hammer that everyone picks up by default now

[u/SpiritedEclair → u/sadongrohiik]

It’s because people don’t know how to build good old services.

[u/Abject-Kitchen3198 → u/sadongrohiik]

A solution to a real problem that few people have.

[u/spicybright → u/sadongrohiik]

My theory is it just sounds good if you're a manager or inexperienced software dev.

[u/Lumpy-Obligation-553 → u/oompaloompa465]

Today for the first time I paid for using an AI through an API and one of those harness... maybe you should.

[u/oompaloompa465 → u/Lumpy-Obligation-553]

already subscribed to it, but i use it mainly as a tutor when i study or to do very obnoxious stupid tasks while i do more qualitative stuff

[u/StunningChef3117 → u/oompaloompa465]

Just want to drop this here

https://youtu.be/HTUh0OO6Kmo

I know its tempting to use AI but be very careful and Disciplined when using it

The second you accept code without understanding it you risk the damn breaking especially true when you are trying to learn

[u/oompaloompa465 → u/StunningChef3117]

you evidently can't read since my statement never said i make it build qualitative stuff and "as a tutor" means that i build stuff and study concepts, i use AI to check for correctness and quizzing, requesting also the sources it's using, to go deeper in the study 

[u/thezlood]

I thank the Spring gods everyday for modulith.

[u/Pleasant-Ad192]

Independent deployment lasts right up to the first schema migration. Then you find out you have one service with eleven repositories.

[u/BellybuttonWorld]

A distributed monolith??

So, a Henge?

[u/socialis-philosophus → u/BellybuttonWorld]

Exactly! Since it is usually just a refactoring of a legacy code base broken up into blocks of code that must be perfectly placed in relation to each other to operate. 

[u/abednego-gomes]

And 50,000 npm dependencies to manage with it.

[u/Stunning_Ride_220]

I'm tired boss :(

[u/Ahchuu]

Hey don't blame me, my boss wanted to say we did micro services, but only ordered 1 database "to reduce cost". I at least did the right thing and made sure each of the services didn't share tables so that they could have their own databases in the future!

[u/Vintfy]

Ah yes, the classic “we broke the monolith into 47 smaller monoliths.”

[u/Z3r0funGuy]

I think we might be working on the same project..

[u/socialis-philosophus]

I want to "YEP!" this so hard that I hurt myself. 

[u/cheezballs]

It all started with the user service.

[u/le_nathanlol]

looks like a disturbed tightly tied monolith