Re:Smithy: A language for defining services and SDKs
by aszen on Friday May 07, 2021 @07:53PM
(#27082176)
The main use case is to auto generate clients for services and even create stubs for service implementations.
AWS sdks need to be implemented in dozens of languages so something like Smithy helps in code gen for multiple languages, avoiding the massively manual task of creating client apis.
Re:Smithy: A language for defining services and SDKs
by jonhohle on Monday May 10, 2021 @04:45PM
(#27110715)
Amazon has done this internally across several different iterations and it's fantastic. Being able to write a service definition and object model and then generating clients and service stubs makes it easy to model what client/server interaction will look like apart from implementation. When I was there, there were at least 3 protocol representations that you could expose for the same model, make it simple to support a variety of use cases.
What's the use of such descriptions aside from diagrams? I realize there's e.g. terraform that use similar kind of language to describe what to create/destroy.