After last week's post, today I will be sharing the functionality Map for the Application. These functionalities/features, I am planning to develop in upcoming days.

Below functionality map image shows the business architecture of the application. The application is divided into multiple modules and each module has various functionalities or engine. The functionality of the application refers to the specific features and capabilities it offers to its users.

The application module may also contain the engine. Engine takes the input data, performs the validation and perform the business actions e.g. Billing engine, which takes the usage data, performs the validation such as data integrity and then generate the bills using price list.

At technical level, each functionality or process engine is represented as microservice and can be interacted with, using APIs. While all the functionalities are defined under module, there can be interaction and dependancies between different functionality blocks.

A microservice is a self-organising container with it’s own business logic, schema, data validations and APIs to interact with other micro-services or applications. Each microservice component performs a specific functionality.

The application map above is currently defined at high level and will be further elaborated at later step.

Do let me know your thoughts/feedback in comments