Modularizing Laravel

Abstract

In the previous chapter, I mentioned that we had hit a sort of roadblock in our development of the claims processing application example we’ve been slowly defining since the beginning of the book. The application we are building has a number of different bounded contexts, a generic subdomain, and a bunch of different modules that encapsulate the various features and components that we need in our application. If we were to use the standard directory structure provided out of the box with a fresh Laravel installation, we would soon find things cluttered, scattered, and almost impossible to maintain once we started building even more complexity into the application when we implement future feature requests.