What might a native NATS service API look like? | RethinkConn '22

Historically, NATS has provided easy-to-use, but fairly low-level client APIs without much guidance on modeling services. As the use case of microservices in the cloud and at the edge has increased significantly in the past 12 months, the NATS team has prototyped a simple API for creating services.
Slides | bit.ly/3XaM3Bb
NATS is a connective technology powering modern distributed systems, unifying Cloud, On-Premise, Edge, and IoT.
Join the NATS Community on Slack: slack.nats.io
Learn More about NATS at docs.nats.io/

[@villagecityorg]

When DePIN software becomes a thing, this off-line first and off-cloud-first will be KING!

[@suikast420]

Could be very interesting as a faas platform usecase. Bu Beyond this ? Can you tell some concrete usecases ?

[@bruradagast]

very curious about this development, and what it can offer over all kinds of SOA that we've seen before since SOAP :)
is it going to be fully schema-agnostic? or it will support some schemas out of the box, e.g. JSON schema?

[@SynadiaCommunications]

The service api is still in a development stage, but as always NATS itself is schema agnostic, the service api may allow you to advertise a schema to users of the service