Changes between Version 70 and Version 71 of SatelliteBigData
- Timestamp:
- 2009/03/20 15:17:33 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SatelliteBigData
v70 v71 115 115 Apart from storage and getting the data out again we briefly discussed how to actually work with these data, i.e. running scripts on them. It is clear that shipment of large datasets should be avoided; it is often much simpler to bring the software to the data instead. 116 116 117 The main message from this discussion was that each database should be optimized for its own data and will therefore be completely different from the next. However, it is the API that can provide interoperability if we can come up with a common set of terms for querying. We believe that current web-technologies like mashups based on very simple APIs like Flickr's can be an alternative to other grid-based approached for integrating data.117 The main message from this discussion was that each database should be optimized for its own data and will therefore be completely different from the next. However, it is the API that can provide interoperability if we can come up with a common set of terms for querying. Also if new web-services can do some levels of processing of the big data before export, this can help with external integration systems. If our new webservices become available using RDF and symantic web technology, it opens the door for multi-layered processing. We believe that current and emerging web-technologies like mashups based on very simple APIs like Flickr's can be an alternative to other grid-based approached for integrating data. 118 118 119 119 == Work group discussion topics ==