Seismic DDMS - Halliburton perspective - Domain API and related topics
Source - @vishal
Expectation is that DDMS will serve applications smoothly with typesafe APIs.
So far, two open standards (oZgy and oVDS) have been brought in. It makes sense to have common API to handle these different types of content storage. Applications then do not have to worry about underlying formats.
Another requirement - because of volume in Seismic data, need multi-part streaming capability.
Halliburton has provided Binary content storage with streaming capability, both input and output. Standards have evolved from HTTP2.
There is also need for access to multiple DDMS's, over and above Seismic DDMS. Common technology to support multiple domains. Halliburton has used Binary storage option.
For Seismic, this should also cover access to SegY as well.
Comments from Paul Quinn (EA team) - APIs need to provide suitable access to large volume data over and above RESTful JSON APIs. Agree about extending access to other DDMS's, Time series data, Relational data, Document store. Need general chunking and binary loading capability. Also, there should not be separate Document Store for any specific DDMS. Should be common, with Core Data Platform.