Apache Fineract CN library to multi-tenant persistence of data and migrations in cassandra

Clone this repo:
  1. 3ae622c Merge pull request #8 from aasaru/gradle_4.10.3 by aasaru · 3 years ago develop
  2. 6aca205 FINCN-179 gradle to 4.10.3, FINCN-178 make Travis build forks by Juhan Aasaru · 3 years ago
  3. fb30580 Merge pull request #7 from aasaru/jfrog by Awasum Yannick · 3 years, 5 months ago
  4. 98b0762 FINCN-148 build with travis-ci.com and upload artifacts to Artifactory by Juhan Aasaru · 3 years, 5 months ago
  5. a4703c1 Merge pull request #6 from myrle-krantz/develop by Myrle Krantz · 4 years, 6 months ago

Build Status

Apache Fineract CN Cassandra

This project provides helps for using Cassandra in Fineract CN services.

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.

Installation

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.