It provides an interface to an underlying infrastructure upon which the component’s service is built. This is the driver-based approach to designing components.Īt the very core, you design the component with extensibility in mind, in a way that allows its default behavior to be replaced by objects that implement the component’s contract.Ī driver is a specific implementation of a component’s contract to a software system. What’s interesting is, you can build components in a manner that allows them to deliver their service in different ways while still providing the same contract it promises. They are modular and are responsible for delivering specific services to an application, say, for example, a Session component that handles states in a web application. Driver-based ComponentsĬomponents are usually entities that enforce separation of concerns in a software system. It encapsulates a set of related functions (or data) into a reusable unit.

A software component is, essentially, a small unit, with usually well-defined interfaces that form the basis of composition for a larger system. Most modern software systems are built by assembling small, self-contained, and reusable entities that provide specific services and functionality to the system.

Laravel as a framework is richly composed of reusable components - some of which are third-party Symfony components - that are all well-defined and pieced together to make up the system. It gives us a plug-and-play approach to building software systems.

It allows us to build large systems that are composed of decoupled, independent and reusable components. Componentization is a great way to build extensible and reliable software systems.

Laravel maker