In my conversations with potential customers and in documentation, I often state that RapidOSS makes it easy to work with external systems. Since "easy" is a relative concept, without some concrete examples this may not mean much to folks who don't have first hand experience working with RapidOSS.
Integration with external systems very often require in-depth understanding of the APIs provided by the external systems. Even when the external system provides standard APIs (SOAP, database etc.) it is not easy to master the variations from the standards, and figure out the structure of the data, how to use it.
In RapidOSS, we use a simple data structure consistently for all external systems. If the data is a single object (record, line, etc.) it is represented as name value pairs, referred to as “Map”. For example, if we want to represent employee information, we could use the following structure:
