LM: In previous versions of IFS, we relied heavily on direct database access or older integration methods. Now, IFS Cloud is “API-first.” Klas, what is the biggest technical hurdle for companies when moving to OData?
KK: The shift to OData and REST APIs is probably the most significant architectural change. In the past, many customers built “tight” integrations that lived inside the database. In IFS Cloud, that’s no longer an option. You must communicate through the API layer.
The challenge isn’t just “rewriting” code; it’s about performance and security. OData is powerful and flexible, but if not implemented correctly, it can lead to latency issues, especially with high-volume legacy systems. However, the benefit is huge: by using APIs, you decouple your systems. This means when IFS releases an update, your integrations don’t break. It’s a prerequisite for the “Evergreen” state we keep talking about.
LM: Many technical teams are worried about the complexity of managing these hundreds of new API endpoints. How does Novacura simplify this transition for a developer who is used to the “old way”?
KK: This is exactly where we provide a massive shortcut. Instead of writing complex, manual code to handle every OData call, we use Novacura Flow as an integration layer. We have a dedicated IFS Cloud Connector that “speaks” OData natively.
It allows you to map your data visually and handles the technical heavy lifting – like authentication and session management – automatically. This means you can keep your legacy integrations running by using Flow as a “bridge” between the old on-premise world and the new IFS Cloud API world. You get the benefits of the cloud architecture without the headache of a 100% manual rewrite of every integration.
December 20, 2024 
6 min to read 
