To enable .NET developers to leverage the scalability, connectivity, and reliability of the InterSystems IRIS for Health™, InterSystems IRIS for Health supports several types of connections to and from .NET applications.
Connect a .NET application to InterSystems IRIS
ADO.NET for relational access
ADO.NET is a data access technology from the Microsoft .NET Framework that enables programmers to access data sources in InterSystems IRIS for Health™ with SQL in a standard, reliable way.
XEP API for high-speed object access
The XEP (Express Event Persistence) API provided by InterSystems enables .NET applications to store and retrieve objects from InterSystems IRIS for Health™. More specifically, XEP projects .NET objects as persistent events, which are persistent database objects that store the state of .NET objects.
XEP is optimized for applications that must handle high throughput, such as transaction processing applications. If you use XEP for object persistence, you can avoid the overheard of object-relational mapping.
Native SDK for direct access to data
The Native SDK for .NET provides direct access to globals, the tree-based sparse arrays that form the basis of the InterSystems multidimensional storage model and underlie the InterSystems IRIS for Health™ object and SQL interfaces. The Native SDK exposes these native data structures, which provide very fast, flexible storage and retrieval. The Native SDK also enables your .NET application to work with InterSystems IRIS for Health objects as easily as if they were native .NET objects, and includes the ability to call InterSystems IRIS for Health class methods and routines.
Entity Framework for object-relational mapping
Entity Framework is a mapping tool that enables you to map .NET objects to relational tables in InterSystems IRIS for Health™ and eliminates the need for most of the data-access code that developers must typically write.
Connect InterSystems IRIS to an external application
Using InterSystems External Servers (for instantiating and manipulating external .NET objects)
Using the InterSystems SQL Gateway (for connecting to external databases via ODBC)
Using the InterSystems ODBC Driver (for connecting to external ODBC data sources)