nballerina VS spec

oh boy -- lot's of work ahead for you folks, best of luck! I'll be watching this project. We do a ton with GCP so when this matures we'll be looking at it more.

How do you compete with -- if at all -- with Ballerina lang? https://ballerina.io/

PS: This advice stems from my personal experience while building BallerinaLang. We spent the first two to three years working with our own bytecode interpreter before we transitioned to JVM bytecode. Our LLVM backend is still under development and has a long way to go.

Considering your rich background in C++ and Haskell, along with your interest in functional programming paradigms, I wouldn't necessarily predict that Ballerina will "blow your mind." However, you might find certain familiar syntax while encountering numerous "why?" questions.

Ballerina actually showed some innovative ways to do it and is an interesting language to keep an eye on... finally, Unison decided to focus on its cloud offering and seamless distributed functional programming. Also a really cool language.

Last week I found Ballerina (https://ballerina.io/) via a comment here on HN, which got me thinking that I've gotten a bit out of touch with newer/up and coming languages in development. My guess is that, if I missed Ballerina before a week ago, I've probably missed quite a bit more.

What have I missed? And it would be cool to see where people are finding these types of things too.

https://ballerina.io/ and https://www.asyncapi.com/ seem like two efforts to move in this direction a bit for web APIs.

Reminds me of https://ballerina.io/

... which looks actually pretty nice, but I suspect the name of the project is a terrible marketing decision that will hold adoption back ¯\_(ツ)_/¯

AsyncAPI: Interested in how to define your WebSocket APIs? One of the most advanced realtime specifications is the AsyncAPI specification, which comes with various generators for code and documentation, as well as renderers for the specifications.

Our journey with FastStream started when we needed to integrate our machine learning models into a customer's Apache Kafka environment. To streamline this process, we created FastKafka using AIOKafka, AsyncAPI, and asyncio. It was our first step in making message queue management easier.

Automatic Docs: Stay ahead with automatic AsyncAPI documentation

FastStream supports in-memory testing, AsyncAPI schema generation and more... If you are interested, please support our project by giving a GH start and joining our discord server.

However, in order for the system to work effectively, there must be a common understanding between the components regarding events and their data structures. This is where AsyncAPI comes in; it helps define a contract that describes how the components communicate and behave effectively.

You can also take a look at https://www.asyncapi.com/ (a spec for asynchronous APIs). It's useful for this use case, that is, building a well structured websocket interface with pub/sub.

Sure! Next step I am working on AsyncAPI scheme generation by your application code. It's also includes a project generation from scheme, scheme web view (lika the Swagger for OpanAPI), etc. It will a much difficult than just another broker implementation...

Onboarding - Enable developers to quickly learn how to consume the exposed APIs. For example, offer OpenAPI or AsyncAPI documentation and provide a portal and sandbox.