fbpx

Why Your Application Should Be Built with a Component-Based Architecture in Mendix?

Mendix is one of the common trends in the Application development era today is the pattern of microservices and component-based architecture, which gives you the ultimate flexibility and scalability. Mendix Applications are built to be on cloud native and containerized, which creates a perfect ecosystem for creating complex Applications with the proper level of componentization and flexibility to grow the application over the time. With the adoption of Cloud Foundry in the market, organizations can easily take advantage of these modern patterns and component-based architectures with a much smaller level of complexity.

An example of how Component-Based Architecture in Mendix concept works in the real world could be a Direct-to-Consumer Quote and Buy portal for an insurance customer. These are often highly complex systems, including integrations, underwriting, payment capture, topped off with the need for a great user experience. In traditional Application development and in other platforms, this would all be built in one huge application, sharing the same hardware, and creating one point of failure.

Mendix enables customers to containerize the aspects of the application into microservices to create independent containers, that can scale horizontally or vertically as needed to manage the load. In our example, we could logically split this into four main components.

  • The Portal Dashboard where customers interact
  • An underwriting component that is deployed as a Mendix App Service
  • A payment capture component that is deployed as a Mendix App Service
  • An integration component that ties the Mendix Cloud to the back-end Policy Admin system

Why Component-Based Architecture in Mendix is important?

In the scenario where you have a huge number of users hitting the application all at the same time and the user experience slows down because of long-running threads in the background and large computations that are consuming memory. One option is to scale the entire Application but rather than scaling the entire Application because of one process would be a waste of resources.

Instead, we could build each component to horizontally scale on the Mendix Cloud based on the resources needed. In this way, if the underwriting engine is taking more time than expected and needs extra horsepower, that specific component can scale up as needed without disturbing user’s experience. Alternately, if an Application has a lot of front-end traffic, but not a lot of back-end processing, the Portal itself can scale to the right leave of the payment, integration, and underwriting engines alone.

Mendix supports other public clouds, for example Mendix Cloud

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.

Menu