The Next Gen
WordPress
Experience!

Conventional monolithic architectures focus on layering code horizontally across functional boundaries and dependencies, which inhibits their ability to separate into functional components. As the Monolith grows bigger, so does the complexity, security loopholes and performance degradation factor. 

A modular monolith however, is configured to combine the simplicity of single process communication with the freedom of componentization. WordPress has fair amount of componentization built-in, but when it comes to how plugins and themes interact with the WordPress Core, it can surely get better than what’s out there – especially when a customized Cloud Compute Engine is involved – like ours. 

Our Architecture establishes a bounded context by segmenting code into individual feature modules (just like plugins, but at WordPress Core level). Each module exposes a interface definition to other modules. The altered definition can trigger its dependencies to change in turn.

Much of this rests on stable interface definitions. However, by limiting dependencies and isolating data store, the architecture establishes boundaries within the monolith that resemble the high cohesion and low coupling found in a microservices architecture. This has helped our  team to parse functionality, but can do so without worrying about the management baggage tied to multiple runtimes and asynchronous communication within the WordPress core.

All this, while being fully compatible to WordPress releases – so that, if you decide to take your website elsewhere, we can provide you all the means to do so (with site data exports).

What we have done is basically customize the WordPress architecture to better suit our Private Cloud Engine. This is not something that is noble and that can be applied to other platforms. We have very high respect and gratitude towards the open-source community for all their contributions to the amazing WordPress platform.