Type safety is extremely important in any application built around a message bus like Pulsar. Type definition and evolution can either be built in the application or relied upon the data layer to support it out of the box allowing the application to only concentrate on business logic, not how of data store and evolution. Apache pulsar offers server as well as client side support for the structured streaming.
We have been using pulsar for asynchronous communication among microservices in our nutanix beam app for over an year in production.
This talk presents the technical details on what is available in the apache pulsar server and client side, how we have used pulsar's schema support to build our use cases and our learnings from them.