Smithy: A language for defining services and SDKs

Post by oblio » Sat, May 08, 2021, 10:40 AM UTC

mtdowling wrote: post #18

peterthehacker wrote: post #6

How 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…

Post by oblio » Sat, May 08, 2021, 10:54 AM UTC

mtdowling wrote: post #35

scrubs wrote: post #32

Pardon my ignorance: once one gets to: https://awslabs.github.io/smithy/quickstart.html#next-steps well, what is it? What was autogenerated? I know JAVA from previous jobs, but not Gradle and whatever the Smithy generated artifacts are to be composed with is unclear to me.

It's not really a fully finished project yet, so not much. We shipped the AWS SDK for JS v3 with Smithy, the AWS SDK for Go v2 with Smithy, and just launched an alpha of the AWS SDK for Rust using Smithy. More are in the works. We're currently iterating on their code generators to make them easier to use outside the AWS SDKs. AWS SDKs are being built in a layered approach where there's a generic code generator that's…

Post by oblio » Sat, May 08, 2021, 11:31 AM UTC

a-dub wrote: post #47

speed_spread wrote: post #38

Earlier quoted context omitted.

Why duck? WSDL still beats the crap out of most newer would-be contract definition standards. OpenAPI is ok, but the tooling comes from all from the same place.

soap was a really good interoperability protocol for adding kilobytes of overhead to simple text based rest rpc where interoperability was defined as being able to interoperate with clients and servers from the exact same software environment. trying to get perl to talk to windows or windows to talk to java or java to talk to perl never really worked at all. but wsdl was like this tempting thing. self describing serv…

Post by martypitt » Sat, May 08, 2021, 11:51 AM UTC

troelsSteegin wrote: post #56

Smithy, Protoforce, Taxi - is the assumption synchronous request/response? OpenAPI has callbacks ( https://swagger.io/docs/specification/callbacks/ ), I am not seeing that in these others. The other thing I am not seeing is a service registry, eg something like UDDI. How do microservices know about each other? Is that a build over common IDL and a coordinated deploy?

Post by RideAndWave » Sat, May 08, 2021, 12:25 PM UTC

smt88 wrote: post #48

RideAndWave wrote: post #46

Earlier quoted context omitted.

We focused on the desktop because it is difficult to use from mobile due to it being an online IDE. I'll take a look, thank you for reporting.

I get your thought process, but two things: 1. If you use flexbox from the beginning, you can easily have basic readability on mobile. 2. A huge % of users will discover things on mobile, even if those things are desktop apps. I wasn't even able to tell what your product is at a basic level.