BASE describes database processing germane to a NoSQL database, such as a data lake. An increasing number of data volumes and variability, according to DAMA DMBoK, spurred the BASE philosophy. Its popularity rose in 2008. BASE provides less assurance than ACID, but it scales very well and reacts well to rapid data changes. BASE construction has three properties:
- Basically Available: The system is guaranteed to be available in event of failure.
- Soft State: The state of the data could change without application interactions due to eventual consistency.
- Eventual Consistency: The system will be eventually consistent after the application input. The data will be replicated to different nodes and will eventually reach a consistent state. But the consistency is not guaranteed at a transaction level.
Other Definitions of BASE Include:
- “A system allowing horizontal scaling, fault tolerance and high availability at the cost of consistency,” (Akshay Pore)
- An alternative to the ACID data processing model. (Dan Pritchett)
- A consistency model that values availability with less strict assurance of consistency than in an ACID database model. (Neo4j)
- An acronym used to describe the properties of certain databases, usually NoSql. (Stackoverflow)
BASE Case Examples:
- Creating a value-based model for a health organization from disparate informational sources
- Using shopping cart applications on a website
- Uncovering fraud rings and scams
- Monitoring network and IT infrastructure security
- Managing and reusing document content
Businesses use BASE Database Types to:
- Use the object-oriented architecture native to the cloud
- Process large amounts of unstructured data very quickly
- Support data research
- Find patterns, such as fraud
- Gain business insights
- Manage data from the Internet of Things (IoT)
Image used under license from Shutterstock.com