Apache Fineract CN library to support tenanted event-sourcing pattern for saving and executing commands POST, PUT, DELETE

Clone this repo:
  1. dbba791 Merge pull request #12 from jupitermoney/upstream by Awasum Yannick · 1 year, 8 months ago develop
  2. fb5d25c Bumped mq and support for authentication. Required is we are using AmazonMQ by Rohit Verma · 1 year, 9 months ago
  3. 3bd10a2 Merge pull request #10 from aasaru/gradle_4.10.3 by aasaru · 2 years ago
  4. 09b22be FINCN-179 gradle to 4.10.3, FINCN-178 make Travis build forks by Juhan Aasaru · 2 years ago
  5. dccf653 Merge pull request #8 from ebenezergraham/FINCN-157 by Awasum Yannick · 2 years, 4 months ago

Apache Fineract CN Core Command Build Status

This project is an umbrella for all Apache Fineract CN Core components.

Abstract

Apache Fineract CN is an application framework for digital financial services, a system to support nationwide and cross-national financial transactions and help to level and speed the creation of an inclusive, interconnected digital economy for every nation in the world.

Prerequisites

Runtime

Install Java 8 as described at https://docs.oracle.com/javase/8/docs/technotes/guides/install/install_overview.html.

Cassandra

Install Apache Cassandra as described at https://wiki.apache.org/cassandra/GettingStarted.

After installation you need to create the meta keyspace:

cqlsh
CREATE KEYSPACE IF NOT EXISTS system_console
  WITH REPLICATION = {
      'class' : 'SimpleStrategy',
      'replication_factor' : 3
  };

Multi-tenancy

Multi-tenancy is reached by providing separate data storage on a per tenant basis.

For every tenant a new keyspace is created internally. A tenant aware component provides transparent access to these resources.

Versioning

The version numbers follow the Semantic Versioning scheme.

In addition to MAJOR.MINOR.PATCH the following postfixes are used to indicate the development state.

  • BUILD-SNAPSHOT - A release currently in development.
  • RELEASE - General availability indicates that this release is the best available version and is recommended for all usage.

The versioning layout is {MAJOR}.{MINOR}.{PATCH}-{INDICATOR}[.{PATCH}]. Only milestones and release candidates can have patch versions. Some examples:

1.2.3-BUILD-SNAPSHOT
1.3.5-RELEASE

License

See LICENSE file.