The 7.1 release is finally out! And here's what you need to know about the new features and updates!
Entando Application Composition Platform Version 7.1 is now available to support enterprises who are modernizing applications to accelerate development, reduce runtime costs, and streamline maintenance through the use of a composable application architecture. Entando brings developer joy to the creation, curation, and composition of modular enterprise applications.
Even before the 21st century, enterprises have been advancing infrastructure and strategies to solve business problems. From the development of web applications on-prem, to their subsequent move to the cloud, and now, modularization in the cloud, each move has accelerated development, lowered cost and streamlined maintenance.
This new phase of modularity focused on decoupling (or breaking up) both the backend code and the monolithic frontend by bundling microservices and micro frontends into Packaged Business Capabilities (PBCs). These PBCs could be shared across development teams and projects within an Enterprise Hub and assembled into applications via a low-code Application Builder, all within a unified Application Composition Platform.
The updates available in Entando Application Composition Platform v7.1 are focused on the pro-code creators. It provides many new capabilities to support the development of modern composable applications, which include:
New: Entando Platform Capability (EPC)
To accelerate application development, Entando 7.1 now supports a pluggable framework to allow Creators and Composers to easily expand the functionality of the Entando App Builder, add external services. Like the PBC, an EPC is a packaged capability and it adds functionality to the platform like menu options or an API management page. An EPC can be a headless CMS like Strapi, that is bundled, stored on Entando Cloud Hub, and implemented in the App Builder.
A sample configuration is shown below:
The headless system (e.g., Strapi) uses the Entando App Builder as a templating mechanism to create and manage pages, content layout, and content versioning.
1) An EPC can be deployed to the Entando Hub (or Entando Cloud Hub, the publically accessible version of the hub),
2) Composers can access and install EPCsinto the Entando App Builder, adding a new menu item to the builder, which
3) when accessed, opens the headless interface, where content can be managed and you can return to the App Builder at any time.
4) Users can access the external system’s APIs and resources, deploying them into applications using the page designer. Many types of EPCs can be built for Entando 7.1, including Headless CMS (Strapi.io is coming soon), Workflow, AI/ML, API Mgmt, and more.
New: Pro-code bundle Templates
v7.1 introduces Pro-code Bundle Templates to enable developers, system integrators, and enterprises to create new Packaged Business Capabilities by reusing existing micro frontends and microservices allowing consistency and acceleration from a core PBC library.
New: Service Discovery
With v7.1, communication between micro frontends and microservices is decoupled and service discovery is made simpler with the API claims mechanism orchestrated by the ent CLI. It eliminates the need to define and manage API endpoints, both in local development and within a running instance.
Updated: Create Tooling
v7.1 mainly focuses on developers. The local development process was improved and now developers can easily initialize a bundle from scratch or download one from a hub. They can add components and populate the bundle descriptor with micro frontends, microservices, and platform components with the ent CLI. They can run,build, and install with only a few commands. Bundles that have worked on 7.0 will work on 7.1 as well. More details can be found here: https://developer.entando.com/v7.1/docs/getting-started/ent-bundle.html#entando-7-1-bundle-development
Updated: Docker Image Specification
Previously, developers used Git repositories to manage both code sources and bundle versioning. Now bundle packaging and publishing has moved to Docker which handle the image specifications. With this, one can still manage code sources on their preferred Git provider but each release will be done through an image registry.
Updated: Entando Command Line Interface (CLI)
We have enhanced the Entando CLI for Mac and Windows. The CLI can now create new bundles from templates downloaded from the Hub, providing a wider range of commands to perform various actions. Some examples:
Updated: Entando Hub
The Entando Hub was introduced in v7.0 and provides a repository for PBCs, solution templates, components, and/or component collections. Enterprises, Development Teams, System Integrators and others can implement an Entando Hub as a central repository from which the Entando App Builder can discover and quickly access entries. Entando Hub updates include:
To learn more about Entando 7.1, or to get started with Composable Applications, see: