If you're familiar with OutSystems, you've likely come across the buzz about OutSystems Developer Cloud (ODC). As this next-generation low-code platform garners more attention, many OutSystems 11 (O11) users are looking to migrate their applications to leverage its full potential. But migrating from 011 to ODC isn’t as easy as it sounds. You have to put in effort and understand the intricacies of the architecture to make the migration process a seamless one. Before diving into the process of migration, lets first understand why it’s important to migrate from O11 to ODC and how does it help organizations?

Migrating to OutSystems Development Cloud (ODC) from OutSystems 11 is important for keeping your applications current and competitive. The visual development environment in the platform coupled with the modular architecture and enhanced features, enables developers to create complex, enterprise-grade applications faster and with less effort.

And what happens with that? It increases the efficiency of the applications and enables organizations to respond more quickly to changing business needs, reduce time-to-market, and foster innovation. It also strengthens security of the applications reducing the IT burden.

In this article understand the differences between O11 and ODC, the architecture, migrations strategies, and the best approaches. With ODC, developers can focus on delivering value to the business, rather than getting bogged down in the intricacies of traditional coding.

What is the difference between ODC and O11

Understanding the Differences: O11 vs. ODC

Architectural Changes

In ODC, the concept of a module or eSpace is replaced with applications and libraries as the minimum units. This change aligns with domain-driven architecture but requires some refactoring to avoid monolithic designs.

Entity Management : Entities can only be created in applications, not libraries. Libraries can include reusable components like blocks and server actions, but they cannot manage entities directly.

Role Management : Roles are now application-specific in ODC, meaning they cannot be shared across applications. This requires a rethinking of role management strategies, especially for roles used across multiple applications.

Application and Library Adjustments

Entities and Screens : Entities and screens can only be created in applications. Blocks, which are reusable UI components, can be created in both libraries and applications but have different access levels.

Service and Server Actions : Service actions (which can be public) and server actions (public only in libraries) are more tightly controlled to ensure modularity and security.

SQL and External Logic : ODC uses Amazon Aurora as its SQL engine, necessitating adjustments for SQL Server/Oracle-specific functions. Extensions are replaced by external logic using AWS Lambda.

Key Changes to Note

Some of the notable changes include the removal of registered role concept and different configuration of anonymous screens. Currently, ODC does not support Business Process Technology (BPT), though OutSystems is developing ODC Workflows and a migration tool. ODC does not support SOAP for exposure, only consumption through custom external logic. The only available system entity is Users, and site properties are replaced with read-only settings.

Read more: A comprehensive guide to OutSystems Developer Cloud

Migration Kit Components

To make the migration process easier and seamless, OutSystems introduced various documentation, tool kits, and guides.

Migration Assessment Tool : This tool evaluates your current O11 applications for ODC compliance, highlighting areas that need modification.

Code Preparation : Using Service Studio, developers address the findings from the assessment tool to prepare the code for migration.

ODC Migration Console – Code Migration : This tool ingests O11 applications, modules, and extensions, converting them into ODC applications. It simplifies the conversion process, especially for .NET extensions.

ODC Migration Console – Data Migration : This tool handles the critical task of data migration, ensuring that all data is correctly transferred from the existing database engine to Amazon Aurora, maintaining data integrity and structure.

Migration Strategies

OutSystems proposes two primary migration strategies:

One-Shot Migration :

This is suitable for small infrastructures with a limited number of applications (up to 300 AOs), this approach involves a single, comprehensive migration process.

Coexistence Approach :

Ideal for larger infrastructures, this strategy involves running O11 and ODC infrastructures in parallel. New applications are developed in ODC, while existing applications are migrated gradually.

Preparing for Migration

While the migration kit’s release is still pending, organizations can begin preparing by aligning their current applications with ODC requirements. This preparation includes:

Refactoring applications to fit the new architecture and module constraints.

Adjusting role management to align with application-specific roles.

Ensuring compatibility with Amazon Aurora for SQL-based operations.

Planning for the transition of business processes and external logic.

Conclusion

Migrating from OutSystems 11 to OutSystems Developer Cloud presents a significant opportunity to leverage the latest cloud-native capabilities. But understanding the architectural changes, preparing your applications, and utilizing the forthcoming migration tools are all intricate and requires expertise.

If you proceed without understanding the architecture, you’ll end up complicating the process even more. If you are looking for a smooth and efficient transition to ODC, we can help you. Drop an email to