OutSystems Developer Cloud (ODC), the latest OutSystems innovative low-code solution, represents the next evolution in low-code development. As a cloud-native application development platform, ODC has undeniable advantages. From high-performance application development and streamlined development processes to scalability on demand and effectiveness. Among numerous others, ODC empowers businesses to accelerate their digital transformation journey, unlocking unprecedented levels of innovation and efficiency.
Take a deep dive into the benefits of ODC for businesses, find more information in our article: Why choose ODC?
However, despite the compelling advantages of ODC, there are circumstances where it’s essential to acknowledge that it might not be the best fit for your organization, situation, or application ββat least currently. In such cases, OutSystems 11 becomes a better option to adopt or to stick with.
The reasons why ODC may not be the best choice for your business
New licenses
For most new customers, ODC is the way to go, as OutSystems believes new applications should be developed strictly in ODC. Nevertheless, this is not the case for specific scenarios:
- Compliance Requirements: If the organization needs to meet specific compliance standards like SOC2 Type II, ISO, PCI, or HIPAA. These are currently available with Sentry in OutSystems 11, but not yet in ODC. OutSystems aimed for ODC to support SOC2 Type II by Q4 2023, with the other compliance standards to follow, but there isn’t information yet if they are already available.
- Data Residency: If the data must reside in a location not yet supported by ODC, the option is OS11. OutSystems continues to add regions to meet customer’s demands.
- Self-Managed Infrastructure: Due to corporate policy, among other reasons, organizations may prefer to run all applications on the infrastructure they manage internally. In this case, ODC may not be the best fit.
- Complex Workflows: While ODC supports simple and medium complexity workflows, it doesn’t offer the same level of complexity as OutSystems 11 with Business Process Technology (BPT), OutSystems’ advanced workflow engine.
In these scenarios, the recommendation is to stick with the powerful OutSystems 11 platform and develop your applications. When OutSystems finds the solutions to tackle the identified obstacles, consider transitioning to ODC.
Existing licenses
The majority of existing OutSystems clients have the opportunity to migrate to OutSystems Developer Cloud (ODC), benefiting from the additional advantages that a cloud-native platform offers. Clients can migrate their applications from OS11 to ODC with the migration tool from OutSystems.
Look into this ITNEXT article to learn more about the migration process and how to prepare for it. The article provides an understanding summary of the steps to take: ODC Migration.
However, ODC isn’t a one-size-fits-all solution. There are cases where it might not be ideal to migrate to ODC immediately. In such circumstances, it may be wiser to wait for new ODC features, particularly regarding developments in the ODC migration tool.
Let’s explore two common scenarios for clients already using the OutSystems platform:
Reactive Applications
If an organization has a set of reactive applications already created, they should all be assessed and revised before being created in or migrated to ODC, prioritizing them based on their complexity level. The existence of each feature in current applications should be checked in ODC, as it might happen that some development needed doesn’t exist yet, like multi-tenancy.
Furthermore, it’s essential to anticipate adaptations required for existing logic and code when transitioning to the new platform. For instance, rebuilt SQL Advanced queries in PostgreSQL, transform server actions into service actions. Adapt the architecture, as the module definition suffers a complete turnaround. Align it to embrace a domain-driven approach. This refactoring approach is for existing applications. For any new applications, the recommended approach is to create them directly in ODCββ if possible.
As you may be concluding by now, this process before migrating to ODC, will require time and resources. Organizations must carefully consider these factors to ensure a smooth transition.
Traditional Applications
If the application is built in traditional OutSystems, ODC is not the answer right away. The OutSystems migration tool is not built to migrate from traditional to ODC, only from reactive. The applications must as well (like in the first point) be assessed, revised, and re-thought while considering best practices and new architecture, code, and logic approach for ODC; and then refactored to OS11 first. Then, if possible, the reactive application can be developed in or migrated to ODC.
Transitioning from traditional applications to ODC requires more time and resources than migrating directly from reactive applications.
For both scenarios, whether dealing with reactive or traditional applications, it will be necessary to expend time and resources for the transition. Rethinking your applications is fundamental to achieving a smooth and efficient transition and maximizing the benefits of transitioning to ODC. If, due to constraints, organizations find themselves currently lacking the resources or time to undergo this process, it may indicate that ODC isn’t the optimal solution at the moment.
License constraints
For creating or migrating apps to ODC, obtaining the ODC license is a prerequisite. This means that at some point you would need to have both OS11 and ODC licenses at the same time. So, organizations must consider the timing and strategy for acquiring these licenses to optimize their investment and migration process.
One approach is to prioritize the refinement and adaptation of existing OS11 applications to align with ODC requirements before obtaining the new license. This ensures that applications are ODC-proof. Once the applications are prepared, organizations can then acquire the ODC license and proceed with the migration process.
Alternatively, it can be very advantageous to acquire the ODC license upfront, so your developers can test it, learn it, and become more familiar with it. This early access can speed up the migration process, when the time comes, by enabling the developers to gain proficiency with the platform, ultimately leading to a more efficient transition.
Another option is to migrate applications incrementally, one by one. In this case, you will need ODC and OS11 licenses. You will need to have both anyway at a certain moment in time. While this approach may incur additional costs, it offers flexibility and allows organizations to adapt their migration strategy according to their specific needs and circumstances.
In the end, the approach you want to follow will depend on your specific situation, objectives, and strategy. By carefully evaluating these factors, organizations can effectively navigate license constraints and optimize their transition to ODC.
Other constraints
Other reasons that can make you want to wait before choosing to migrate your applications to ODC are similar to the considerations applied to new licenses:
- Feature Availability: Not all features available in OS11 may be present in ODC. This is important if an application depends on an unavailable feature, with no replacement (yet) in ODC. OutSystems’ roadmap for delivering the features is not defined. They recommend to wait for the release.
- Business Process Technology (BPT): one of the features in OS11 not supported by ODC, as it does not yet support complex workflows. However, implement simpler or medium-complexity workflows with the recent release of Events. This new feature is an example of OutSystems’ efforts in providing the available features in OS11 and the ones required by clients.
- Cloud-Native Deployment: ODC is a cloud-native development platform, meaning it is only accessible via the cloud. If an organization’s applications are built on-premise, transitioning to a cloud-based environment may pose challenges, depending on corporate policies and other factors. In such cases and if it is not possible to migrate to the cloud, migrating to ODC is impossible.
It’s important to note that the constraints associated with ODC are temporary, with OutSystems actively working to address them, except for the cloud vs on-premise situation.
The decision to migrate should be based on careful consideration of these factors, with organizations advised to wait until any temporary constraints are resolved before proceeding with migration. By exercising patience and strategic planning, organizations can ensure a smooth and successful transition to ODC when the time is right.
In conclusion, while OutSystems Developer Cloud offers competitive advantages in low-code development, organizations must carefully assess their unique needs, existing infrastructure, and strategic objectives before embracing ODC. While it represents a significant advancement in cloud-native development, it’s not a one-size-fits-all solution and requires thoughtful consideration and evaluation.
If you need help auditing your current situation and determining the best approach, get in touch! We will accompany you on this adventurous, yet rewarding journey. Our team of OutSystems expert consultants and developers have the skills to guide you and explore the best choice for your specific case. Let’s explore this ODC cloud-native world together and unlock the full potential of your digital transformation journey!