"Ballerina makes it easy to create resilient services that integrate and orchestrate transactions across distributed endpoints."
Is it real or a joke? It sounds like a markov chain generator was fed with tech mumbo jumbo and then generated this?
If it's real - what is the no nonsense description?
And who is behind it?
Its a real language :-). Please check the spec out here: https://ballerina.io/res/Ballerina-Language-Specification-WD....
Feedback welcome!
We just made a 0.970.0 release last week which contains significant alterations. The language and runtime have been in iterative design and test for a couple years.
We are just now putting live ballerina.io so that we can start working within the community to gain adoption. A number of WSO2 customers are working with it in development and pre-production, but we asked them to not consider production deployments until the rework was done.
We hope to hit a 1.0 milestone by the end of the year where we will guarantee backwards compatibility.
We do find the runtime to be extremely stable with throughput numbers about 5x higher than equivalent ESBs, and we are running long term stability tests that are doing well. We'll publish all of these results soon, too.
These are all capabilities that are usually built into integration products around a language, though these concepts are baked into the syntax and the language design.
The platform portion contains additional runtimes components for enabling this functionality including an API gateway, a message broker, a transaction coordinator, and a bridge for brokering transactions to services that are written in other languages.
There are roughly 100 committers. It's a lot of people that were involved in Apache Synapse and WSO2 ESB.
