D365 Modern POS (MPOS) Simplified Architecture

Above diagram is showing MPOS simplified architecture with its main components:

MPOS Client 1/2 with Local Hardware Station and Database:
• On left side we can see two MPOS machines are running with local hardware station and database (for offline mode) installed in each machine.
• Actually MPOS supports dedicated and shared hardware station both. Dedicated is recommended due to stability and easy to use but we can use shared hardware station as well. 
• Different peripherals devices are connected with terminals like printer, scanner, MSR etc.
• MPOS has local CRT and Database for offline mode. Once it will not be connected to Online Retail Server then it will work in offline mode through CRT.

MPOS Connected with Server on IIS Cloud/Local:
• On right side we can see that MPOS is connected with server, hosted on IIS (Azure Cloud).
• MPOS can be connected with local IIS in case of RSSU (Retail Store Scale Unit).

Retail Server Hosted Cloud/Local:
• On right side we can see retail server hosted on IIS (Azure Cloud) which is providing data to MPOS. MPOS is calling Retail server for performing CRUD operations on database.
• Retail Server can be hosted on local IIS in case of RSSU (Retail Store Scale Unit).
• Retail Server is comprised of a set of APIs which can be accessed in order to perform operations through POS or online stores.
• It Consists of ODATA API due to which retail server can be connected to any application and supports advance authorization and authentication.
• Retail Server uses CRT for handling data from database. Retail server just holds ODATA request from client and parse it into CRT objects and pass to CRT and then CRT query database.

Commerce Runtime (CRT):
• CRT is part of Retail Server and also hosted with retail server on machine.
• Commerce Runtime is the core engine which performs all the core business operations and contains the business logic for retail.
• It is comprised of multiple layers that are data access layer, workflow layer, service layer and API.

Database (Channel Database / Store Database / Brick and Mortar Database):
• Channel database has multiple names wrote in above heading.
• It will save all data of POS/Online Store or any other client which is calling by Retail Server.
• Channel database will be called from CRT.

D365 Cloud POS (CPOS) Simplified Architecture

Above diagram is showing CPOS simplified architecture with its main components:

POS Client 1/2 with Shared Hardware Stations:
• On left side we can see two POS machines which are running CPOS with shared hardware station installed in separate machine.
• Actually CPOS supports shared hardware station but we can setup on each machine separately and make it local sharing. 
• Different peripheral devices are connected with hardware station like printer, scanner, MSR etc.

CPOS Hosted on IIS Cloud/Local:
• On right side we can see that CPOS website hosted on IIS (Azure Cloud) which can be browsed from everywhere.
• CPOS website can be hosted on local IIS in case of RSSU (Retail Store Scale Unit) which can be browsed over an organization intranet.

Retail Server Hosted Cloud/Local:
• On right side we can see retail server hosted on IIS (Azure Cloud) which is providing data to CPOS. CPOS is calling Retail server for performing CRUD operation on database.
• Retail Server can be hosted on local IIS in case of RSSU (Retail Store Scale Unit) which can be browsed over an organization intranet.
• Retail Server is comprised of a set of APIs which can be accessed in order to perform operations through POS or online stores.
• It Consists of ODATA API due to which retail server can be connected to any application and supports advance authorization and authentication.
• Retail Server uses CRT for handling data from database. Retail server just holds ODATA request from client and parse it into CRT objects and pass to CRT and then CRT query database.

Commerce Runtime (CRT):
• CRT is part of Retail Server and also hosted with retail server on machine.
• Commerce Runtime is the core engine which performs all the core business operations and contains the business logic for retail.
• It is comprised of multiple layers that are data access layer, workflow layer, service layer and API.

Database (Channel Database / Store Database / Brick and Mortar Database):
• Channel database has multiple names wrote in above heading.
• It will save all data of POS/Online Store or any other client which is calling by Retail Server.
• Channel database will be called from CRT.

D365 Cloud POS (CPOS) VS Modern POS (MPOS)

Retail Cloud POS (CPOS):

• Cloud POS is a hosted version of the POS application.
• Cloud POS is Online POS, Offline POS functionality does not support to               CPOS.
• It can be open in Internet Explorer, Edge & Chrome.
• It can be hosted on Cloud or Local environment. That's why it is available to     everyone everywhere.
• It has responsive design that's why can be open in mobiles, tablets and PC's.

Retail Modern POS (MPOS):

• Modern POS is an application that is packaged, installed, and serviced on         device. 
• Modern POS supports online and offline modes.
• It can be installed on Windows 10 and later.
• It can be installed on Local machines and can connect with Cloud or Local         server.
• It can be installed on Windows PC's, Android and IOS mobiles.

Main differences between CPOS and MPOS:

• Cloud POS is Online POS while MPOS supports both online and offline               functionality.
• CPOS is open in browser while MPOS is installed in device.
• MPOS is faster than CPOS in performance.
• CPOS has only shared hardware station while MPOS has both shared and         dedicated hardware stations.
• CPOS has many cache issues due to browser while MPOS has no cache issue.
• CPOS configured very quickly while MPOS needs some time to configure due to installation process.