Is this supposed to generate the language bindings too from the Smithy schema? How is that done? Can't seem to find info on that in the Guides or examples.
Smithy: A language for defining services and SDKs
21–30 of 77 posts
Re: Smithy: A language for defining services and SDKs
#22what ever did happen to wsdl?
ducks
Re: Smithy: A language for defining services and SDKs
#23what ever did happen to wsdl? ducks
JSON
Re: Smithy: A language for defining services and SDKs
#24Re: Smithy: A language for defining services and SDKs
#25How does this compare to Google’s protocol buffers? [0] It looks like smithy has a broader set of applications. [0] https://developers.google.com/protocol-buffers
Protobuf and gRPC are great, and AWS will continue to make sure developers can be successful using them with AWS. I’ll try to explain how we ended up at Smithy instead of using other existing tools. We started working on Smithy around 2018 because we wanted to improve the scale of our API program and the AWS SDK team to deal with the growing number of services (over 250 now!) and languages we want to support in offic…
The history and origins help frame the Smithy use case for others and where it may not apply. Thanks for sharing!
Re: Smithy: A language for defining services and SDKs
#26Couldn't find a way to generate models for Python - not sure if that is because it doesn't exist or I just cant find it. The code gen part seems a bit under documented.
Re: Smithy: A language for defining services and SDKs
#27Couldn't find a way to generate models for Python - not sure if that is because it doesn't exist or I just cant find it. The code gen part seems a bit under documented.
No Python codegen yet. Our plan is basically that as we migrate AWS SDKs to Smithy, we'll also offer generic client generators too. The Python migration hasn't started yet.
Re: Smithy: A language for defining services and SDKs
#28How does this compare to Google’s protocol buffers? [0] It looks like smithy has a broader set of applications. [0] https://developers.google.com/protocol-buffers
Protobuf and gRPC are great, and AWS will continue to make sure developers can be successful using them with AWS. I’ll try to explain how we ended up at Smithy instead of using other existing tools. We started working on Smithy around 2018 because we wanted to improve the scale of our API program and the AWS SDK team to deal with the growing number of services (over 250 now!) and languages we want to support in offic…
Does Smith support describing OAuth ?
Re: Smithy: A language for defining services and SDKs
#29We've built a similar thing at https://www.protoforce.io, which auto-generates client and server side. It actually transpiles, parsing the models definitions and emits actual code with a bit of shared runtime.
Good amazon opened up their stuff, there should be more competition on this front.
Re: Smithy: A language for defining services and SDKs
#30Smithy structure definitions don't have field indexes like in protobuf or thrift. It also has required fields, where proto3 intentionally did away with them.
How do these differences impact backwards-compatibility-safety of Smithy schema changes?