Entando brings clearer separation between design and runtime tasks
You asked for greater separation between design time and runtime tasks in Entando.
We’ve been listening.
Since Entando first launched, design time and runtime tasks have been mixed together, both physically in the UI as well as logically. We’ve left the choice of which state to perform a task in up to the individual developer. It was a successful approach and it helped to create the product that Entando is today.
But times change, and it’s time that Entando does, too.
With the upcoming Entando 5, you will begin to see clearer separation. Most significantly, this means a more nimble deployment process that allows you to make selective deployments instead of redeploying the entire project after every modification to your code.
The new decoupled Entando 5 App Builder opens the doors to developing applications more in line with our stance on Modern Applications. Runtime updates give Entando greater flexibility to develop microservices, the deliverables that are ultra-lightweight and unburdened by extraneous features. These, in turn, lead to developing effective CI/CD and DevOps-centered processes because you can design them and make them run in different environments without needing to rebuild the application every time.
The CMS will be available in Entando 5 as part of our legacy application stack and we'll be placing an emphasis on further developing it for future versions of Entando. We’re confident that the extra time spent will go towards launching a best-in-class product that will encourage further DevOps approaches.
We have some work ahead of us. It’s a real transformation and we’re making our way there. You’ll begin to see the changes when we release Entando 5 at the end of May. In addition, expect more detailed, technical posts about upcoming features as we get closer to the release date.