Some of the most common software architecture styles applied with Energy Management Services — Core Platform

Client-server

A peer-to-peer architecture that consists of a client, which requests a service, and a server, which provides the service. Example: The EMS-CP can implement a server able to optimize the natural gas logistics.

Microservices

A distributed architecture that decomposes an application into small, independent, and loosely coupled services that communicate through well-defined interfaces. Example: The EMS-CP orchestrates a larger task in several jobs in its internal.

Model-view-controller (MVC)

A user interface architecture that separates an application into three components: the model, which represents the data and business logic; the view, which displays the data to the user; and the controller, which handles user input and updates the model and view accordingly. Example: The EMS-CP can be used to implement the model component in a day-ahead market simulator.

Event-driven

An asynchronous architecture that relies on the production and consumption of events, which are messages that indicate a change in state or occurrence of an action. Example: The EMS-CP can receive events from the services in charge to monitor XBID daily products.

Layered

A hierarchical architecture that organizes an application into layers of abstraction, each of which provides a set of services to the higher layer and depends on the lower layer. Example: The EMS-CP can perform mid-term day-ahead scenario analysis in a BI platform.

For more details on how the Energy Management Services — Core Platform can support the growth of your business, please dive in at this link: https://www.dedanext.it/ems-core-platform-the-predictive-analytics-software-that-supports-your-investments/