[linuxdude314]

Do you not version APIs you design?

When engineering an API meant for consumption by disparate services it’s imperative to provide back words compatibility.

This is pretty basic stuff anyone designing a serious API should be taking into account.

[dzhiurgis]

Sure we do, it's been /v1.0/ for the last 2 years!

[habibur]

All API that I am running had been v1 the whole time.

[nurettin]

Yes, and I have to consult with other teams when versioning, I don't just go "welp here's the next version I created and deployed without asking anyone because that's what the IBM microservices manifesto (2006) suggested and some random guy on HN insinuated I'm causing undue friction if I work with you guys"

[scottious]

sure, but all of that is a cost which you don't have to pay with a monolith. Versioning APIs and having to constantly think about backwards compatibility with independently moving services is not trivial.

Sometimes the cost is worth it. Most of the time it's not

[TameAntelope]

Oh, you absolutely have to pay that cost with a monolith, it's just less clear and obvious because you can change all of the consumers when you make a change to an interface.