Concepts and Practical Introduction - Part 1

we can define an application follow Microservices architectural style as an application consist of suite of small specialized services running independently and communicate with each other , if needed , using lightweight mechanism.

For example , if we talk about order management system for brokerage firm , how we can make such system follow Microservices architectural style ??

first thing you need to look to the business using  bird's-eye view. what business modules my system consist of , here is a list for example

• User Module
• Order module
• Portfolio management module
• Market communication module
• reports module

these are basics business modules i can think of right now , let’s say also we have a base infrastructure module , let’s call it

• Web Module

User module is responsible for user management

Order module responsibility to apply business rule and validations for user’s orders ,

Market communication module responsibility to communicate with exchange market to submit orders and receive results ,

Portfolio module responsibility is hold users stocks and liquid cash ,

Reports module responsibility is to provide reports about current user position and also about historical transactions.

Web module is the base module to aggregate functionalities from different services and present them in one web application to the end user.