The infrastructure deployment time machine
It all started 8 years ago during EuroPython 2017 when Will introduced me to QUADS 1.0 and how their whole client-facing inventory and UI was relying on a heavy WordPress dependency. I was adamant that if I ever joined the team I would replace WordPress with a proper Python web service.
Continue reading “The Evolution of quads-web”
A few weeks ahead of schedule, QUADS 2.1 brings immense improvement and simplicity to QUADS design by removing our WordPress component entirely and serving all automated wiki/inventory/visuals natively via quads-web
Big design improvements are coming in QUADS 2.1 by completely removing our WordPress component and bringing everything directly back to Flask / quads-web. This greatly reduces our design complexity and adds a plethora of foundational improvements for future features.
We decided to take a first try hands-on approach following the future QUADS roadmap and re-architect our legacy landing/requests portal application, previously a trusty LAMP stack, into a completely rewritten Flask / SQLAlchemy / Gunicorn / Nginx next-gen platform. What worked in Dev/Stage however had serious problems in production with CPU bottlenecks – this is our journey.
Continue reading “The Curious Case of the CPU Eating Gunicorn”
QUADS Project 