"it has the ability to affect HTTP traffic as it flows through"
Software applications and their development, management, orchestration, administration, maintenance and general wellbeing have moved to the web. Okay don’t write in just yet, those are just the opening credits. Obviously then, we have started to apply web-centric technologies to these applications in order to push them towards …
We are seeing a massive increase in load on web architectures across the board. With mobile device proliferation, wearable computing, digital TV and the Internet of Things...
...but mostly from botnet traffic. Vuln scans, brute-force login attempts, and plain old (D)DoS.
Techniques for web acceleration include caching, compression and “prefetching”
...and throwing more hardware & electricity & Moore's Law at it. Those are the only things you can do squeeze some performance out of a web architecture that's frankly unmanageable, based on weak standards and sloppy HTML with error-tolerant syntax and embedded client-side scripts, generated by a big ball of PHP or possibly some other "slow but agile" (and fragile) script lang such as Python or Ruby, with rampant dependencies.
So yeah, devops can stop the buck-passing between dev and ops. That's a very real problem. The much bigger problem is that we're all stuck with this crap architecture called the WWW. There's gotta be a better way to disseminate information.
As for server side technology, thankfully I wrote my last world-facing PHP script last decade. mod_php + MySQL is out. Now it's all about writing applications in your choice of modern language, and reverse proxying from your webserver / load balancer.
Reusing shared resources such as templates and cached database results in an event loop style application is hundreds of times more efficient.
Overall I like the hodge-podge of organically evolving web architecture. Because the only realistic alternative is a single vendor propitiatory walled garden.
Biting the hand that feeds IT © 1998–2019