Do I have to use a specific frontend technology on Entando?
No. One of the key advantages of a micro frontend platform is the ability to select the frontend language or technology that matches your environment. Do you already have an experienced Angular team? Angular it is. Does your new frontend lead prefer React or Vue? Go for it. Do you want to mix the work of different frontend teams into a single application? Entando enables you to do exactly that.
Does Entando provide ready-to-use components?
Yes. Entando comes with some basic components that you can use to build your applications. However, the beauty of Entando is that you can build your own components and reuse them repeatedly in your organization to best meet your needs.
Where can I deploy Entando?
Entando can deploy to a private cloud, public cloud, or on the local infrastructure that makes sense for your use case. Entando provides out-of-the-box deployment on AWS and Azure using Kubernetes. Entando also provides images and documentation for deploying on OpenShift. Additionally, we provide Docker images, extendable base Docker files, and examples that use Docker Source-to-Image (S2I). In most cases, including the cloud cases above, Entando is deployed in a J2EE container like JBoss EAP, Wildfly, or Tomcat.
Do you support high availability (HA) architecture?
Yes, Entando supports an HA architecture.
What is the Entando Component Repository?
The Entando Component Repository allows you to automatically install your Entando components for quick reuse in all of your Entando applications.
How can I migrate from one version of Entando to the next?
Every migration is different. As a platform, Entando allows our users and customers to build their own software and so there will be migration considerations for the Entando components of an architecture as well as the customer-developed components. Migrating the core elements of the architecture to a new version should be relatively straightforward.