Base-one of the cornerstones of high-availability architecture

Author: fenng | reprinted. The original source and author information and copyright statement must be indicated in hyperlink form during reprinting.
Web: http://www.dbanotes.net/arch/base_arch.html

When discussing the scalability best practices of eBay, I mentioned "> base mechanism. More and more architects are paying more attention to "> base strategies (of course, I am not saying"> acid doesn't matter)

"> The base strategy was proposed by Eric A. Brewer of Inktomi (which has been acquired by Yahoo! Since tomorrow's yellow flowers) in 1988. The acronyms are defined as follows:

• BAsicallyAVailble-basic availability
• SOft-state -- soft state
• EVentual consistency -- Final consistency

"Soft State" (SS) corresponds to "hard State" (HS. I have hardly found a clear definition. But with the description in the RFC-1633, "soft state" can be understood as "connectionless", and "hard state" is "connection oriented", so much clearer.

Eventual consistency is also the ultimate goal of "> acid. For a large architecture like eBay, it is guaranteed by powerful message bus capabilities.

For a large architecture like eBay, please refer to the prose of Dan Pritchett of eBay in the latest technology: Base: An acid alternative. Pay attention to the event-driven mentioned in this article) architecture.

We believe that in the next few years, base will become a technology buzzword. Of course, acid is not outdated, but they must be appropriate.Application scenarios. With the openness of internet technology, more often, an architect needs to repeatedly measure appropriate application scenarios.

"> BTW:" acid "refers to" acid "in English, while" base "refers to" Alkali ". Acid-base can be mixed together.