Note |
---|
title | Draft: Work in Progress |
---|
|
This document is subject to change without notice. |
Introduction
Apache Fineract (simply “Fineract”) is built around a multitenant, service oriented, and tiered architecture, and can be deployed in a SaaS (Software as a Service) model or on-premises.
...
The main design principle of the Engine is CQRS ( Command Query Responsibility Segregation ), a pattern that separates commands and queries into different models and services. This approach has multiple benefits: 1) State changes (commands) are persisted, providing an audit of all changes, 2) fine grained control and extension of state changes, and 3) scalability based on consumer behavior and real system load.
...
- Database caching stores records on the database level and is useful for reporting, batch jobs, and low level SQL queries.
- 2nd Level caching stores data objects on the application level and keeps database turnarounds on a very low level allowing fast in-memory access of frequent data.
Architecture (in 2020)
The Engine’s architecture was designed with a focus on modern, scalable and extensible technologies ready to run in the cloud. All components where were selected based on their maturity, proven reliability and cost efficiency.
It is our goal to provide a software that is deployable with effectively no cost that can grow with the customer need over time using well known best practices and support from a wide range of communities.
The basic Fineract Financial Service Engine Fineract architecture is as follows:
Resource | Component | Comment |
---|
Operating System | Linux, Windows, Mac OS | Amazon AWS image and Debian package available |
Runtime | Java |
7.x >=11 |
|
Application Server | Tomcat |
7v9.x | Embedded Tomcat for development environments |
Database | MySQL 5. |
x7 | Embedded MariaDB for development environments |
Application Framework | Spring Framework |
4 Hibernate 4 4 1 2