workloads in which reads are much more common than writes). Fast Processing: ZooKeeper is especially fast in "read-dominant" workloads (i.e.Simple Architecture: The architecture of ZooKeeper is quite simple as there is a shared hierarchical namespace which helps coordinating the processes.
Reliable System: This system is very reliable as it keeps working even if a node fails.Some of the prime features of Apache ZooKeeper are: ZooKeeper was developed in order to fix the bugs that occurred while deploying distributed big-data applications. These servers communicate with the client machines to provide them the information. ZooKeeper is modeled after Google's Chubby lock service and was originally developed at Yahoo! for streamlining the processes running on big-data clusters by storing the status in local log files on the ZooKeeper servers. ZooKeeper is used by companies including Yelp, Rackspace, Yahoo!, Odnoklassniki, Reddit, NetApp SolidFire, Facebook, Twitter and eBay as well as open source enterprise search systems like Solr. The ZooKeeper Atomic Broadcast (ZAB) protocol is the core of the system. ZooKeeper can be viewed as an atomic broadcast system, through which updates are totally ordered. Clients can read from and write to the nodes and in this way have a shared configuration service. ZooKeeper nodes store their data in a hierarchical name space, much like a file system or a tree data structure. The clients can thus ask another ZooKeeper leader if the first fails to answer. ZooKeeper's architecture supports high availability through redundant services.
0 kommentar(er)
