3 ms·
Which is surely an argument for "never start a project using microservices"? Who knows exactly what their interfaces are going to be, across their entire proje
by marcus_holmes 6y ago
Which is surely an argument for "never start a project using microservices"?
Who knows exactly what their interfaces are going to be, across their entire project, on day 1, and gets that right every time?
- com2kid 6y ago> Who knows exactly what their interfaces are going to be, across their entire project, on day 1, and gets that right every time? Same problem exists for binary interfaces, or source code interfaces. Or for a client system that talks to a cloud service. Or for a cloud service that exposes APIs for other cloud services to call. Technologies exist to version APIs. It is sad that JSON is the standard interchange format, since it is pretty miserable at this entire problem.
- marcus_holmes 6y agoI agree completely, but all this is exacerbated if you have to make your interfaces immutable from the first version
- jeffbee 6y agoThey aren't immutable. You can safely add fields and you can add methods or entire services. It is easy to change microservice interfaces, you just do it in a particular way.
- jeffbee 6y agoGod forbid anyone should sit down for an hour and think through their interfaces before furiously typing.
- marcus_holmes 6y agohehe this is so true. But still. The problem is more in the requirements. I've never, in >25 years commercial coding, met a business problem described accurately enough that I could nail the design first try.