¶ The main differences between Run-Odoo and Odoo.sh
¶ Server and infrastructure
Infrastructure / Server / Instance: While Odoo.sh is using the same server to execute multiple Odoo services for different clients simultaneously, Run-odoo proposes a 1-client <-> 1-Instance model. This comes with immediate benefits:
Better security and compliance when assessing the segregation of the data between different clients.
Better performance since all the resources allocated by Run-Odoo to their clients are dedicated and not mutualized or “shared” as Odoo.sh names it.
Higher reliability and resilience with Run-odoo. In case of technical failure, infinite loops, or python memory leaks from one the deployments or addons of one client, the other instances cannot be contaminated and there is no possible propagation.
Different computing resources for DEV / STAGING / PRODUCTION: With Run-Odoo, each instance you subscribe to has its own workers. On the other hand, Odoo.sh is using the same infrastructure workers to propel the DEV, the STAGING, and the PRODUCTION of the same project, which brings in its trail performance-related issues when all the environments are simultaneously being used and under pressure.
¶ Network and security
- Web Antivirus Firewall WAF: Since Odoo is a web-based online platform, it is constantly under the scrutiny and pressure of bots, web crawlers, and hacking attempts of all sorts. This becomes even more relevant when clients are using the WEB modules to offer services or products for sale. When analyzing the inbound traffic, one quickly realizes that:
- There is a real security issue that OWASP compliance alone does not suffice to tackle.
- The Odoo workers and the PostgreSQL service are spending a ridiculous amount of resources and computing power to fulfill requests from NON LEGITIMATE users or bots attempting to POST, GET, download, crawl or inject from behind fake VPN or remote foreign IPs. This takes a heavy toll on the system and end up compelling the clients to “add more workers” so that legitimate clients can get a decent service.
- Run-Odoo comes with integrated CloudFlare WAF services and advanced bot filtering mechanisms that allow it to evade and block all non-legitimate traffic before it can even begin to affect the Odoo system.
- CDN: Run-Odoo comes with integrated CloudFlare CDN features allowing you to benefit out of the box of the following improvements (detail here)
- Lossless and Lossy Image Optimization
- Accelerated Image Delivery for Mobile
- Prioritized Loading of Key Site Assets
- Content Prefetch for Google Search
With this feature, your Odoo Service static contents (CSS, images, icons, pictures, etc…) are automatically made available and distributed by the CloudFlare CDN. This means not only that you get better loading performance anywhere in the world but also that your Odoo instance needs to produce less effort and consume less bandwidth. This makes this feature very valuable for Odoo deployments using WEB features for portals or E-commerce solutions where graphics and picture loading times are crucial.
- Anti-DDoS and anti-DoS: Run-Odoo comes with integrated CloudFlare Anti-DDoS mitigation (details here). This protection blocks and mitigates attacks in real time. Coupled with the Run-Odoo specific defense strategy and extra rules maintained specifically for Odoo defense and protection, you benefit out of the box from a world-class service that will bring the following benefits:
- Sensible decrease of Server resource consumption due to drastic filtering of all inbound queries and systematic elimination of harmful and persistent automatic access and attacks from “non-clients”
- Specific Odoo-adapted extra defense strategies and filters limiting all standard injection, spoofing, and authentication attacks.
- An ideal “territorial presence”: Run-Odoo is indeed benefiting from the coupled presence of both Digital Ocean and AWS (Amazon Web Services) infrastructures, which allows users to pick geographical locations for their deployments that match the following 2 criteria:
- COMPLIANCE with PRIVACY: Many countries and customers shall impose that their data be hosted in the country where the solution is run.
- LATENCY / ACCESS TIME: The closer to the user, the better. The only way to achieve a low latency is to be located as close as possible to the end-users / clients of the Odoo solution.
