Welcome to the Jmix documentation!
|Please note that Jmix is currently in preview. We are working on finalizing features, stabilizing API, bugfixing and documentation.|
Jmix is a high-level framework for enterprise web applications. It comes with advanced tooling and a rich set of functional modules.
Jmix is best suited for creating data-centric applications with a complex data model and rich user interface. It is a full-stack framework in the sense that it provides support for creating both the backend and UI of your application.
Jmix is based on Spring Boot, which is a de-facto standard for creating enterprise Java web applications. It means that you can use a lot of third-party libraries and frameworks with minimal configuration, in addition to the functionality provided by Jmix.
Jmix itself consists of a number of fine-grained modules that you include in your project using starters, as you would do for any Spring Boot application. All modules except the core one are optional, so you can have only dependencies that you really need.
Jmix Studio is a plugin for IntelliJ IDEA that helps you at all stages of the application development: creating and configuring a project, defining data model, generating database migration scripts, developing UI screens in a visual editor. It provides advanced navigation, code completion and inspections specific to Jmix projects.
Jmix provides a convenient way of working with one or multiple relational databases. With some additional effort, you can connect to any data source like a no-SQL database or an external API.
Developing with Jmix usually starts from defining the data model. Jmix Studio creates the database schema from the data model automatically, and when your data model evolves, Studio helps you synchronize the database schema with the model by generating database migration scripts. If you have an existing database already, you can generate the data model from your database schema, also with the help of Studio.
Jmix is based on Spring Framework, so use Spring beans to create the business logic that works with your data model.
As soon as you have some entities in the data model, Studio can generate UI screens for CRUD operations on the entities. Then you can customize the UI in many ways: change the layout, add and remove visual components, adjust the data loading.
You can use any frontend technology to work with Jmix backend through its Generic REST or custom endpoints of your application.
Moreover, Jmix provides two specific options for rapid creation of the user interface:
The downside of this technology is limited scalability: the backend side of the UI is stateful and consumes the amount of resources proportional to the number of concurrent user sessions. So Backoffice UI is suitable when you have a predictable and not very high (up to tens of thousands) number of users working with the system at the same time.
On the other hand, the entry barrier to the Frontend UI is higher if you don’t have experience in frontend technologies, and the speed of development is usually lower. This differentiation is amplified by the fact that currently Studio supports Backoffice UI much better than Frontend UI.
Choosing UI is not an "either-or" decision: you can use both technologies in your project. For example, you can quickly create a bunch of administrative screens for internal users of your application with Backoffice UI, and develop a more polished UI with specific functionality for external users using Frontend UI. Both UIs in this case will work with the same data model and business logic.
Check out the Using Studio section to get more information about Jmix Studio features and installation options.
The rest of the documentation is organized by topics:
The Add-ons section describes additional modules that provide out-of-the-box functionality to your project.
Appendices contain some reference information and the Migration from CUBA guide.