Technical Deep Dives
Performance, scale, reliability — for engineers.
Performance, scale, reliability — for engineers.
A reading shelf. Articles ship when they earn their place.
Technical Deep Dives are for engineers. The PostgreSQL tuning that fixed a slow report. The Docker config that cut Deploy Monkey's cold-start. The Odoo customisation pattern that survives version upgrades. The xterm.js + WebSocket integration that became the live web shell. These are the deep technical writeups — code samples, configurations, profiling output included — that you can actually use.
Deep Dives assume technical fluency. They do not dumb down. They are not introductions or explainers. If you're an engineer who wants to know exactly how a thing works, this is the category.
The Enterprise/Community line isn't a feature list. It's a boundary that runs through the things engineers build on, and a module that works in Enterprise dev can fail silently on Community.
Read the articlejQuery is no longer in Odoo's core JavaScript bundle. Custom code that still assumes a global $ is one page-load away from a console error, and the replacement is three patterns, not one library.
Read the articleA technical walkthrough of why a production Odoo instance degrades over time — unindexed queries, computed-field storms, ORM N+1, attachment bloat, cron contention — and the diagnostic order we use to find the actual cause.
Read the articlestore=True is one keyword. It is also, more than any other single decision, what determines whether an Odoo schema stays fast at scale or quietly rots.
Read the articleOdoo's real-time layer has finished its migration from HTTP longpolling to WebSocket. Custom code that still talks to the bus the old way stops getting answers in 19.
Read the articleEvery Odoo major version is a tax. Whether that tax is a week or a quarter is decided years earlier, by five customization habits that separate upgrade-safe code from a rewrite.
Read the articleA casualty list, not a feature list: the specific things in custom Odoo code that stop working when you move from 18 to 19, ordered by how loudly they fail.
Read the articleTechnical Deep Dives connect to the technical depth of Cloud & DevOps, Integrations & Data, and our products (Deploy Monkey, Timenzo, the Odoo Modules). Where the product pages describe what something does, Deep Dives describe how it's built.
Adjacent surfaces: Products for the things we operate; Architecture Notes for the decisions behind the depth.
Real questions from your operating reality become real articles. Send them.