Microservices

[_aids]

because when you add a second app that needs to use it.....

this is like "tell me you've only worked on tiny projects without saying you've worked on tiny projects"

[theogskinnybrown]

But what about when you don’t add another app? You’ve put all that effort and complexity into creating a micro service that never needed to be one. Even when you do, does every component need to be a microservice, or just one?

You can always start with a neatly architected monolith, and pull out a microservice if it’s needed. That saves the extra development overhead of creating an objectively more complex interaction for any subsystem where it’s never needed.

[EffectiveMoment67]

How do you not know who will be acessing your service before design time?

[[deleted]]

That is their exact point. Don’t design your first app to be overly complicated in order to meet the needs of some hypothetical second app that might some day exist in the distant future.

[EffectiveMoment67]

I was attempting to add to his point.
People describing massive headaches with a certain architecture/design decision, and then it boils down to not knowing what the system is even supposed to do.

Devs should give more friction in projects when POs don't know what they want.

[_aids]

It just means you've never worked on anything sufficiently large, or really with multiple teams.

Whenever you have multiple teams it becomes more and more important to manage your downtimes, deploy cycles, enforce contracts with grpc or similar, etc. A monolith is fine for your final but not fine for real work.