After writing a series of posts on the 20-day approach for the AEM Development ( here ), I think it is a good time to delve deep into AEM's building blocks. One of the major technology that AEM uses is OSGi (Open Service Gateway Initiative). Therefore, in the few upcoming posts, we will be learning the OSGi concepts in detail along with code examples. Let's get started! 🙋 Software Modularity In modern times, a complex software can be thought of as a collection of various modules or components. These modules are normally independent of each other and modification in one module does not affect the other modules. These modules interact with each other via an API. The API is defined as a set of classes and methods which can be used from other components. If a module uses an API from another module, it has a dependency on the other module, i.e., it requires the other module exists and works correctly. A module which is used by other components should try to k
Learn all about AEM development. The best place for the newbies to start and a good refresher for the experienced AEM developers. These blog posts will eventually be moved to my new revamped website - https://redquark.org/