Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage CAP Theorem Content on InfoQ


RSS Feed
  • The Blockchain and the CAP Theorem

    Yaron Goland, Principal Architect at Microsoft, has published an article describing how a blockchain client can be made AP or CP based on its implementation. This works by being able to configure how many blocks must come after a transaction until it is accepted. The more blocks which have occurred after the transaction, the more likely it is to have a system wide consensus, making it consistent.

  • Google Launches Cloud Spanner Public Beta

    Google has launched the public beta for Cloud Spanner, its globally distributed relational database service. Part of Google Cloud Platform, it delivers both ACID transactions and high availability, appearing to violate CAP theorem.

  • Questions About the Lambda Architecture

    In a blog post suggesting limits to the usefulness and applicability of the Lambda Architecture, Jay Kreps argues that Lambda contains valuable ideas but that ultimately it is a temporary solution due to immature tools rather than the future of big data.

  • Alternatives to Eventual Consistency

    Causal Consistency models offer an alternative Eventual Consistency for distributed systems; both models should be weighed against your system's requirements and risk tolerance.

  • BitCoins Lost, MongoDB and Eventual Consistency

    The recent theft from several BitCoin operators has sparked a debate whether eventually consistent databases are useful or not for banking.

  • FoundationDB NoSQL Database Supports ACID Transactions

    FoundationDB database platform combines NoSQL scalability with ACID transactions across all data within the database. FoundationDB team announced last month the availability of its new NoSQL database platform.