Definition
A monolithic application is a single unified system in which all functions - user interface, business logic, data access - are packaged and deployed as one unit. Monoliths are straightforward to start with: a single codebase, a single databaseOrganised collection of structured information stored and accessed electronically - foundation of all digital systems., a single deployment. However, they grow complex over time: changes to one module can unexpectedly break others, teams step on each other's code, and deploying one small change requires releasing the entire system. Scaling is binary - you scale the whole system, not just the componentA replaceable part inside a fixed asset. It has its own age, its own history and its own service life - independent of the asset it sits in. under load. Many of the established KISCustomer Information System - the core system at power suppliers and grid companies for customer management and billing. systems in the Norwegian power industry are monolithic systems built on the architectural paradigms of the 1990s and 2000s. They are stable and feature-rich, but difficult to integrate with, slow to update and costly to adapt to new regulatory requirements. ModularArchitecture or design principle where systems are built from independent, interchangeable components. architecture and microservicesArchitecture where an application is split into small, independent services that communicate via APIs. are the alternatives - but the transition away from a monolith is demanding and high-risk.