2 ms·
We had standardisation at the protocol level for the internet which let us build services on top, but now we're looking for the same at the app level. HTTP was
by asim 6y ago
We had standardisation at the protocol level for the internet which let us build services on top, but now we're looking for the same at the app level. HTTP was meant for web pages, we never created anything for Apps and Services. What that new standard is going to look like, I have no idea, gRPC does well to define the APIs and so we use it across dozens of services here https://github.com/micro/services https://github.com/micro/services. Curious to hear what others think will happen.
- carapace 6y agoFWIW, my $0.02: I think this problem has been noticed and solved over and over again. If you squint a little stuff like CORBA are in the same stew pot, eh? There's relatively recent work on collaborative editing and CRDTs, but as it says in the Wikipedia entry: > The first instance of a collaborative real-time editor was demonstrated by Douglas Engelbart in 1968, in The Mother of All Demos. Widely available implementations of the concept took decades to appear. https://en.wikipedia.org/wiki/Collaborative_real-time_editor#History_of_key_products https://en.wikipedia.org/wiki/Collaborative_real-time_editor... There are a lot of these protocol/API tools like gRPC, Thrift, Swagger/OpenAPI, or even good old ASN.1, eh? To me the question is how to drive convergence? How to alleviate https://xkcd.com/927/ https://xkcd.com/927/ ? (The "Standards" comic.) Who shall forge the "one true ring to bind them"? - - - - Also, I think Data Model catalogs (like "Data Model Patterns: A Metadata Map" by David C. Hay) should be part of the answer. Instead of rolling your own data models you should be able to just pull models from a standard catalog. - - - - In sum, if we're lucky, we'll start to get convergence in the protocol and model space. Anything that isn't working towards convergence is just adding another log to the burning pile of standards, eh?