As a developer we often require compound objects (an object build out of a multiple other objects). A SKU with product, price and content information for example. Caching becomes even more important now that many companies move to cloud based database services that have relatively high latency times. Although caching was (and often still is) seen as an afterthought, one should consider the scope of a new project and perhaps BEGIN with caching as the foundation of the project. Having the right caching integrated into your project from the beginning often not only speeds up processing and improves customer perception, but can simplify development by a factor while at the same time shorten project development time and reduce data costs significantly.
Read more...
Complex\distributed systems often have requirements that dont sit well with "clean" architectures. For example we have to integrate legacy api's or we have websock communication to the clients. We want testing right! and lets through in some scripting for household tasks like archiving some of our databases.
There are 2 ways to go about this. Multiple instances of laravel or build versioning into your existing laravel instance.
tldr; use seperate laravel instances
