Intel OpenVino and IBM Red Hat Select IVAAP to Demonstrate the Power of New Hybrid Cloud OSDU Data Platform
This offering powers a unified environment to drive AI, accelerated data analytics, and high-performance computing (HPC) integrated with IVAAP Data Visualization platform. IBM and Red […]
Rethinking ML Integration to Deliver a User Experience with a True End-to-End Geoscience Workflow
For E&P companies, the next challenge in their digital transformation — once their data has been properly stored, indexed, enriched, and cataloged in the cloud […]
How to Extend the IVAAP Data Model with the Backend SDK
The IVAAP data model was created after researching the commonalities between the industry data models. However, when we built it, we kept in mind that each data store carries its own set of information, information that is useful for users to consume. This is why we made “properties” a part of the data model itself. From an IVAAP SDK point of view. “Properties” is a set of name-value pairs that you can associate with specific entities within the IVAAP Data Model.
Deploying IVAAP Services to Google App Engine
One of the productivity features of the IVAAP Data Backend SDK is that the services developed with this SDK are container agnostic. Practically, it means that a REST service developed on your PC using your favorite IDE and deployed locally to Apache Tomcat will run without changes on IVAAP’s Play cluster.
While the Data Backend SDK is traditionally used to serve data, it is also a good candidate when it comes to developing non-data related services. For example, as part of IVAAP 2.8, we worked on a “gridding” service. In a nutshell, this service computes a grid surface based upon the positions of a top across the well of a project. When we tested this service, we didn’t deploy it to IVAAP’s cluster, it was deployed as a standalone application, as a servlet, on a virtual machine (VM).
