OutSystems ODC vs OutSystems O11
What’s the difference and which one is best for your business?
This article describes a highlevel difference between these two rapid application development platforms, which one to use, and what to consider when adopting O11 and ODC, for more information reach out directly.
It’s more important than ever for businesses to rely on systems that can scale applications to meet the needs of millions of users, at the same time that features are built and delivered with a short time to market. To meet these demands OutSystems currently offers two platforms: OutSystems Platform O11 and ODC.
What are OutSystems ODC and OutSystems O11?
- OutSystems platforms to support developers in building and delivering rapid high performant mobile/web applications that scale.
What are the unique characteristic of OutSystems O11 and ODC?
- OutSystems ODC is a native cloud platform that introduces a different approach to developing and operating applications when compared to O11 (at code design and infrastructure architecture).
What are the differences between OutSystems ODC and O11?
- Application Architecture — applications in O11 consists of several modules (used to organize logical layers) in ODC code is incorporated.
- Database Queries — data in ODC is managed by AWS Aurora PostgreSQL (object relational database), whereas in O11 it can link to an SQL Server, Azure SQL Database or Oracle (relational DB systems). (more info here)
- User Management — user management in ODC is handled within the same console for both organization users and end users, in O11 two different interfaces exist for each group of users. (more info here)
- Run time operations — in ODC apps and components are deployed in distributed containers with a communication model for integrations interactions that differs from O11 (same server cluster).
When to use OutSystems ODC instead of O11?
- ODC can be used when handling applications with unpredictable load.
How does low-code platform ODC impact developers?
- OutSystems ODC provides developers with an accessible development environment interface, quite similar to the one used in OutSystems O11.
- However, ODC requires knowledge upgrade in particular on designing applications (at scale). Whilst it can be achieved with relatively little effort, some traditional development practices might become obsolete, as example technical requirements of app interoperability architecture.
How to migrate OutSystems O11 to ODC?
- Plan an assessment of existing applications for migration or re-build.
- Design the applications’ architecture considering ODC requirements.
- Build applications considering one time or phased migration approach.
Discover how ODC transforms the future of software development:
- Guide to Adopt OutSystems Developer Cloud (ODC)
The ultimate goal of OutSystems ODC is to accelerate application response times by allowing companies to build highly available systems features that can scale up without downtime during peak seasons providing positive customer experiences. While OutSystems O11 has been around for a long time and continues to evolve for the purpose it serves, it will eventually be replaced by a new flagship platform model. For now OutSystems ODC and OutSystems O11 share the same purpose: empowering people and organizations to build applications that enhance business productivity.
As you can read, implementing a suitable strategy to develop existing or new applications can be significantly challenging. A subject matter expert can provide an efficient execution. This is where I can help you, providing guidance and solutions’ development. If you’re interested learning more visit my company website or reach me in Linkedin. Thanks for reading!
