This section discusses ObjectGrid in the context of databases.

Does ObjectGrid integrate with a database to automatically invalidate cached data?

ObjectGrid is not an object relational mapper. It does not know where the data in the ObjectGrid came from. An application or an object relational mapper can place data in an ObjectGrid. The ObjectGrid does not know where the application OR mapper got the data. It is the responsibility of the source of the data to make sure that it stays consistent with where the data came from. This means ObjectGrid cannot invalidate data pulled from a database automatically. An application OR mapper can do that and it is the responsibility of the application or OR mapper to provide this function and manage the data stored in the ObjectGrid.

ObjectGrid can front end a database

A Loader can be coded that pulls uncached data from a database and writes changes back to it. The developer of the Loader is responsible to ensure that data in the ObjectGrid is kept consistent with the database.

ObjectGrid used as a cache for Object Relational Mappers

ObjectGrid can be plugged into any object relational mapper that has a way to integrate it. It is the responsibility of the object relational mapper to remove cached data if needed when database data is changed.