tailieunhanh - NoSQL Database Technology: Post-relational data management for interactive software systems

Dynamicity of participants: Some P2P systems, such as [10], assume a fixed set of nodes in the system. However, one of the greatest potential strengths of P2P systems is when they eschew reliance on dedicated infrastructure and allow peers to leave the system at will. Even under these conditions, participants typically have broadly varying availability characteristics. Some peers are akin to servers: their membership in the system stays largely static. Others have much more dynamic membership, joining and leaving the system at will. In a configuration where original data is distributed uniformly across the network, including on nodes that frequently disappear, it may become impossible to. | CoucHBase NoSQL Database Technology Post-relational data management for interactive software systems NOSQL DATABASE TECHNOLOGY Table of Contents Summary 3 Interactive software has changed 4 Users - 4 Applications - 5 Infrastructure - 5 Application architecture has changed 6 Database architecture has not kept pace 7 Tactics to extend the useful scope of RDBMS technology 8 Sharding - 8 Denormalizing - 9 Distributed caching - 10 NoSQL database technologies 11 Mobile application data synchronization 13 Open source and commercial NoSQL database technologies 14 About Couchbase 14 2 2012 COUCHBASE ALL RIGHTS RESERVED. NOSQL DATABASE TECHNOLOGY Summary Interactive software software with which a person iteratively interacts in real time has changed in fundamental ways over the last 35 years. The online systems of the 1970s have through a series of intermediate transformations evolved into today s Web and mobile applications. These systems solve new problems for potentially vastly larger user populations and they execute atop a computing infrastructure that has changed even more radically over the years. The architecture of these software systems has likewise transformed. A modern Web application can support millions of concurrent users by spreading load across a collection of application servers behind a load balancer. Changes in application behavior can be rolled out incrementally without requiring application downtime by gradually replacing the software on individual servers. Adjustments to application capacity are easily made by changing the number of application servers. But database technology has not kept pace. Relational database technology invented in the 1970s and still in widespread use today was optimized for the applications users and infrastructure of that era. In some regards it is the last domino to fall in the inevitable march toward a fully-distributed software architecture. While a number of bandaids have extended the useful life of the .