Mongo Entity provides developers with entity and controller classes for storing entities entirely in a MongoDB collection. It eliminates the need for a base table, or any SQL queries at all; an entity's ID, name, properties, and any field data are all written directly to MongoDB. It also provides classes for embedded entities: entities that are stored as subdocuments in a parent collection, but that can be managed using the standard Entity API CRUD methods, as well as found with EntityFieldQuery. Ultimately, loading a parent entity should automatically load and embed all its child entities, with only one query to a single MongoDB collection.
Mongo Entity is for developers. It provides no interface, nor does it alter the behavior of existings sites out of the box. Modules can use the provided MongoEntity and MongoEntityController classes in hook_entity_info to store entities in MongoDB, rather than a SQL database.
Minimal configuration. Save custom Entities entirely in automatically generated MongoDB collections. No SQL tables needed.
Performance boost. Field data is stored with the Entity in MongoDB, reducing the need for complex JOINs and multiple database queries to load a single object.
Display various types of content, such as blocks, with an accordion-like behaviour. Items in accordion groups will initially appear 'collapsed' with only their titles showing. Clicking an item's title will 'expand' that item to show its whole content, and collapse any other accordion items in the same group. Group items into distinct accordions by simply naming them so that pages can have multiple accordions, each containing multiple types of content.
Provides an option to force-disable WYSIWYG on all text field types that have 'Text processing' set to 'Filtered text' and hence can use WYSIWYG). This is useful if you still want to use text formats, but don't want to have the WYSIWYG, rather than creating all new duplicate text formats just to enable/disable WYSIWYG.