3 ms·
lol, really don't want to be in the same sentence as Urbit so please no. Everything is defined as protobuf interfaces, which is a standard used by Google and e
by asim 4y ago
lol, really don't want to be in the same sentence as Urbit so please no.
Everything is defined as protobuf interfaces, which is a standard used by Google and everyone else now that gRPC is so dominant. So the idea is, define the API in protobuf, code generate and implement the handlers for it. The service can be called by other services on the platform using that code generation and then an API Gateway, which Micro provides can be used to call services externally using the same format but using HTTP/JSON.
To take that even further, M3O (m3o.com) codifies protobuf to openapi specs and then generates client libraries on top. You can see some of that in https://github.com/m3o/m3o https://github.com/m3o/m3o.
- davidjfelix 4y agoTotal tangent, but gRPC is not dominant and I think that belief is cargo-cultism.
- simonw 4y agoYeah I've managed to avoid gRPC for my whole career to date, and I've done a LOT of work on web services and microservices.
- throw827474737 4y agoThanks, that made now more sense. I'd put this condensed together with https://micro.dev/blog/2022/09/27/real-world-micro-services.html https://micro.dev/blog/2022/09/27/real-world-micro-services.... more prominently to the readme of https://github.com/micro/services https://github.com/micro/services ! Looking at that github alone makes it hard to commect the context.
- asim 4y agoThanks I will do that!