System and method for clean bloc architecture state management

A method for performing architecture state management in a software architectural pattern that follows a bidirectional data flow, the method comprising:

• triggering, by a view layer, an event corresponding to one of the plurality of applications based on user interactions on a user interface (UI) widget of the view layer;
• displaying, by the UI widget, a current state of the application;
• receiving, by a business layer, the event from the UI widget;
• in responsive to receiving the event from the UI widget, performing, by a business logic unit of the business layer, a plurality of business logic operations for a plurality of use cases;
• maintaining, by the business logic unit, the current state of the application;
• producing, by the business logic unit, an updated state of the application based on the received event and the current state of the application;
• sending, by the business logic unit, the updated state of the application to the view layer;
• reactively updating, by the view layer, the UI based on the updated state of the application;
• and
• accessing and modifying, by a repository, data from a plurality of data sources.

A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for performing architecture state management in a software architectural pattern that follows a bidirectional data flow, the method comprising:

• triggering, by a view layer, an event corresponding to one of the plurality of applications based on user interactions on a user interface (UI) widget of the view layer;
• displaying, by the UI widget, a current state of the application;
• receiving, by a business layer, the event from the UI widget;
• in responsive to receiving the event from the UI widget, performing, by a business logic unit of the business layer, a plurality of business logic operations for a plurality of use cases;
• maintaining, by the business logic unit, the current state of the application;
• producing, by the business logic unit, an updated state of the application based on the received event and the current state of the application;
• sending, by the business logic unit, the updated state of the application to the view layer;
• reactively updating, by the view layer, the UI based on the updated state of the application;
• and
• accessing and modifying, by a repository, data from a plurality of data sources.