4 ms·
You know how we have an overabundance of ways to design, describe, develop, and document rpc-based distributed systems like REST and microservices? Why isn't th
by cratermoon 6y ago
You know how we have an overabundance of ways to design, describe, develop, and document rpc-based distributed systems like REST and microservices? Why isn't there anything like that for event-driven, message-based systems? If there's a message bus in your architecture, it's usually just a pipe-shaped widget on a diagram. There's dozens of tools that can describe and API down to the finest detail, like swagger/openapi, uml, C4. We have infrastructure as code (helm charts, etc).
In all of them the events and message buses are kind of an afterthought. Everything seems geared towards request-response systems, and nothing adequately deals with the range of event systems and message flows.
- jdkoeck 6y agoHi, you’ll be pleased to learn about the AsyncApi initiative! https://www.asyncapi.com/ https://www.asyncapi.com/ Haven’t looked into it too closely but it looks promising
- cratermoon 6y agoThank you!