InfoGrid is a Web Graph Database with a many additional software components that make the development of REST-ful web applications on a graph foundation easy.
• (Blob) Store abstraction w/ a variety of implementations
• RDBMS joins (e.g. ﬁles, MySQL, Hadoop, S3…) and automatic mapping don’t scale
• Conceptual model/schema w/ run-time enforcement
• Tables are not web native at all
• Most of the data important to applications lives elsewhere infogrid.org
• Graph traversal instead of joins
• All data objects automatically have a URL (REST-ful);
• Tables are not multiple output representations for each URL web native at all
• Objects can change type(s) at run-time
• Cached in memory until not needed any more
• XPRISO and Probe framework automatically make important to external data appear as local/native applications lives
• Automatic/adaptive, incremental updates w/ events elsewhere • Library of Probes infogrid.org
• Library of Probes Plus: GUI template framework, complex traversals and events, ability to distribute P2P-style, modules, identity awareness
Contact for Pricing
Small (<50 employees), Medium (50 to 1000 employees), Enterprise (>1001 employees)
InfoGrid is a Web Graph Database with a many additional software components that make the development of REST-ful web applications on a graph foundation easy. InfoGrid is open source, and is being developed in Java as a set of projects. As powerful as InfoGrid is, it derives much of its power from just a handful of core ideas. Users can develop perfectly ﬁne InfoGrid applications with applying just the ﬁrst two ideas. But the more of these code ideas users apply, the more value users get out of InfoGrid.
All information in InfoGrid is represented as objects, called MeshObjects. Each MeshObject has a unique identiﬁer, which typically is a URL. Users can access any MeshObject in an InfoGrid application by typing its URL into the browser, or do the equivalent from user application code using an InfoGrid API. MeshObjects can relate to each other. By relating MeshObjects to each other, users can construct arbitrarily complex molecules of information from atomic MeshObjects. InfoGrid takes a different approach that turns out to be very consistent with how the web works: the information at any given URL on the web can change its type many times. A MeshObject is, conceptually, the object at that URL. So it makes sense that MeshObjects can change their type without being deleted ﬁrst. In InfoGrid, types deﬁne which properties an object carries. So once users bless a MeshObject with a type, it might start carrying a few properties initialized with default values. Which properties those are depends on how users deﬁned the type. Types are deﬁned in as InfoGrid models. In InfoGrid, choosing a persistence alternative is essentially a conﬁguration step, not a programming step. The InfoGrid project also has developed code that stores MeshObjects in Amazon’s S3 and in Hadoop. No application logic changes are necessary.