Smithy has something called event streams that send async datagrams: https://awslabs.github.io/smithy/1.0/spec/core/stream-traits....

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).

Thank you. Some new vocabulary with Smithy: Prelude, Shapes, and Traits (https://awslabs.github.io/smithy/1.0/spec/core/model.html ). With all the evolution, the lineage story would find an audience, I bet.

Its not exactly what youre atter but smithy has waiters https://awslabs.github.io/smithy/1.0/spec/waiters.html

> 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.

Taxi+Vyne gives you a complete service registry, so both users and systems can discover services and data.

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.

Thank you. Your recent blog post (https://blog.vyne.co/rethinking-api-consumer-patterns/ ) was a positively interesting read. I wonder if there's a query analyzer a ways down the road ...

For protoforce, we provide completely asynchronous server and client SDKs for scala and nodejs, also we suport websockets as a transport.

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.