4 ms·
> Interestingly, the concept of PHP prevents exactly such problems, as a monolith written in PHP only ever executes the code paths that are necessary for the re
by pphysch 4y ago
> Interestingly, the concept of PHP prevents exactly such problems, as a monolith written in PHP only ever executes the code paths that are necessary for the respective workload.
This is just lovely when you have hundreds of PHP endpoints written by your predecessors and each endpoint has rewritten an arbitrary slice of the stack (usually data model layer) because there is no common code path required. Refactoring anything below the html layer becomes impossible.
In fact, calling it a software monolith is misleading, because each PHP script is its own little microservice with poorly-defined API boundaries.
- withinboredom 4y agoHmmm. When was the last time you wrote php? One file per route has been outdated for over 10 years.
- pphysch 4y agoThis particular codebase I am maintaining is 10-20 years old. The point stands. Isolated code paths are great until you have to care about the ways they are not actually isolated (e.g. common database, platform-specific code, etc.).
- withinboredom 4y agoI wasn’t arguing that, just arguing that that is quite an unusual approach in modern php.