3 ms·
I've said a few times that modern microservice architectures feel a lot like what traditional object-oriented programming was about, and I think this is another
by Zababa 5y ago
I've said a few times that modern microservice architectures feel a lot like what traditional object-oriented programming was about, and I think this is another confirmation of that. I think that these days the connectors are JSON over HTTP, RPC and things like that. When a service exposes a JSON over HTTP API, I can use it from any programming language, from any program.
So "first class connectors", to me, would be something like a language describing how to interact with a service, and a code generator that takes that language and transform it into code in your language. For example, the aws-sdk-rust [1] says:
> The SDK is code generated from Smithy models that represent each AWS service. The code used to generate the SDK can be found in smithy-rs.
Here's a link to Smithy's homepage: https://awslabs.github.io/smithy/ https://awslabs.github.io/smithy/.
To me, Smithy with a code generator looks like a connector that would increase your productivity. But I'm not sure if we can call something that relies on code generation "first class". I'm not sure what "first class connectors" would look like either.
[1]: https://github.com/awslabs/aws-sdk-rust https://github.com/awslabs/aws-sdk-rust
- Jupe 5y agoVery cool - thanks for sharing; I'd not seen Smithy before (and was quite curious how AWS manages it "all"!) From the web page: > A Smithy model enables API providers to generate clients and servers in various programming languages, API documentation, test automation, and example code. Yes. This. Please.