Re:How to Start Using Microservices
by marcus_holmes on Monday August 17, 2020 @12:49PM
(#24189000)
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?
> 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.
Re:How to Start Using Microservices
by marcus_holmes on Monday August 17, 2020 @02:19PM
(#24190109)
I agree completely, but all this is exacerbated if you have to make your interfaces immutable from the first version
They 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.
God forbid anyone should sit down for an hour and think through their interfaces before furiously typing.
Re:How to Start Using Microservices
by marcus_holmes on Monday August 17, 2020 @02:18PM
(#24190096)
hehe 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.
To change your RPC protocol in a distributed system, you may add optional fields to the request but you must not add required fields nor change the semantic meaning of any field. You can add new services and methods but you must not disable one that anyone calls.