GroverDB uses standard database architecture to build your database.
- Objects: Every noun - a person, place, or thing - can be represented as an object. Customers, products, machines, events are all considered Objects.
- Classes: Each Object can be organized under a Class - employees and customers could be placed under a People Class. Classes define what Attributes every Object under that Class will have. Every Object must belong to a Class.
Classes may also have Sub-Classes. The People Class may have Staff, Customers, and Investors as Sub-Classes. Any Attribute that applies to the Class will also apply to all Sub-Class.
- Attributes: Any defining feature that describes an Object is an Attribute. If an Object is a noun, then an Attribute is an adjective. Items such as birthday, product color, or even the product name is considered an Attribute of that Object.
- Status: Every Class can also be defined by a Status. Statuses can be thought of as stages in a process. An employee may be a new hire, in training, full-time, or terminated. Every Object will have a Status. For Objects that don’t logically follow a process, their Status can be set to Active or In-Active.
- Multiple Classes: An Object can belong to multiple Classes. For example, a person may be a Board Member Class, a Customer Class and a Founder Class. This would mean the Object would inherit the Statuses and any other feature defined by all Classes. For example, a pet dog may want to be defined under both the Pet Class and the Canine Class.
Connections: Objects can be connected to other Objects, based on how they’re connected in real life - a product is connected to the customer who ordered it; an employee is connected to an event they attended. Connections are made and viewed using the Connection Viewer.