InterSystems IRIS Demo: .NET Object Persistence with XEP

You can store .NET objects in InterSystems IRIS using the XEP API, which enables high-performance object persistence and retrieval. It analyzes .NET classes to automatically generate corresponding database schemas for rapid data handling.

The XEP API provides a faster alternative to traditional ORMs like Entity Framework by directly handling .NET object persistence on InterSystems IRIS, satisfying the need for speed in performance-critical, real-time scenarios.

XEP imports schemas by analyzing your .NET classes and automatically generating the corresponding ObjectScript schemas within InterSystems IRIS, allowing immediate object storage and SQL querying without manual database mapping.

Yes, but XEP is designed as a faster alternative to ORMs like Entity Framework. While Entity Framework handles complex object hierarchies, XEP prioritizes high-speed object persistence and retrieval for performance-critical scenarios.

Yes, you configure a Visual Studio project and add the InterSystems.Data.XEP.dll reference to connect to your InterSystems IRIS instance, import schemas, store .NET objects, and query them using SQL.

You should avoid XEP if your scenario prioritizes managing complex object hierarchies over speed, as it is designed as a faster alternative to traditional ORMs for performance-critical, high-speed object persistence.