Our aim is simple: unleash creativity by making it super simple for all to build and own reactors, via the DSL Reactive Platform. Accelerate microservices architecture, testing and development.
Diesel Apps can be used in the cloud / online, deployed on-premises or embedded as a library, with the configuration local or synced from the cloud.
See more about Memberships.
When carefully selected and used, Domain-Specific Languages (DSLs) may simplify complex code, promote effective communication with customers, improve productivity, and unclog development bottlenecks. Martin Fowler
However, for a DSL system to scale to the enterprise, there are certain thresholds of adoption and certain features it must implement, like:
DSL can enable a much better involvement of the user and business analysts into the final product! Breaking free of being boxed into a UI with limited interactivity and limited options, allows massive creativity.
Most configuration is today either
DSL offers a much more compelling story here! We will explore that and show you how it can be done!
Reactive (or asynchronous) programming was the only way to make something useful out of a big computer, some time ago (interrupts, exceptions, traps what-have-you).
For the longest of time, we switched to a thread-based model, which made programming these interactive and high-performance systems easy.
Yet, reactive programming is not the easiest:
It's all a matter of choosing the right languages, the right technologies and the right patterns and paradigms. We can work through these and figure out the best ways to think reactive!
Yeah, it is. I find software does not get easier to use, especially on the development side: the software designed to create more software.
The software industry is in a sorry state and we're trying to manage our way out via agile project management, reduced quality, reduced scope etc.
Everyone knows that the last 20 percent of the functionality costs 80% of your budget but nobody seems focused on that first 80% of the functionality, which does not require complexity. Not a lot of focus on "rapid application development" or "serious prototyping". Those that are, do not seem reliable or performance-oriented enough.
Let's see if we can find the right set of technologies, scripts, configurations and whatever else we need to make the whole thing tick and purr like a diesel engine!
Here are some ideas to evolve by simplifying things:
Wikis can bridge the gap between content and configuration. Between configuration and code. Between UI and system....
Here are some of the projects that are the stepping stones leading up to this platform:
12 Greenbriar Crt, Aurora,