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?
This is currently used in Amazon S3, Kinesis, Transcribe, and other services.
Smithy doesn’t have a service registry today. However, models can be vended and shared via Maven. Client codegen was designed explicitly to not require coordinated releases of clients and servers (that’s impossible for AWS SDKs).
> Waiters are a client-side abstraction used to poll a resource until a desired state is reached, or until it is determined that the resource will never enter into the desired state.
I havent seen them put behind an async interface but it seems like a good match for a lot of StartWork, DescribeWork(token) patterns.
Because Taxi lets you describe how data from services relate, Vyne can work out how to connect services together automatically, and handle the integration for you. This is a realisation of the UDDI concept, where systems can autonomously work out how to operate with each other.
Java sdk is built on Futures, so somehow it's async as well.
Also we support server-to-client calls, which, effectively, are a better alternative to callbacks.