At the microXchg 2016 conference, held in Berlin, Germany, Uwe Friedrichsen presented a deep-dive into “real-world consistency explained”. Friedrichsen referenced multiple academic papers and discussed topics such as ACID vs BASE, his belief that many developers may not fully understand consistency guarantees with a typical SQL database, and how consistency affects microservice systems.
FoundationDB has announced the general availability of SQL Layer, and ANSI SQL engine that runs on top of their key-value store. The result is a relational database backed up by a scalable, fault-tolerant, shared-nothing, distributed NoSQL store with support for multi-key ACID transactions.
The team behind CockroachDB, an open source datastore project, has recently announced its initial alpha version. Inspired by Google’s Spanner project, CockroachDB aims to address the current lack of an open source, scalable, geo-replicated, ACID compliant database.
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.
RavenDB 2.0 was recently released with several new features. In an InfoQ exclusive interview, Oren Eini (Ayende Rahien), founder and project lead of RavenDB, shares the rationale behind various decisions in the project, as well as what’s coming up.
FoundationDB is a database that provides ACID guarantees along with high performance and availability normally associated with NoSQL databases. In an InfoQ exclusive interview, we learn more about the project from one of the founders, Nick Lavezzo.
During the PASS Summit 2012, a technical conference for SQL Server professionals, Microsoft announced Hekaton, an in-memory row-based data management system targeted at transaction processing (TP) workloads. Besides the advertised increase in TP speeds of up to 10x for old applications and up to 50x for new optimized ones, Microsoft touts Hekaton as being fully integrated into SQL Server.
Bill Heinzman spoke at the recent JavaOne conference about bridging cross-platform transactions between enterprise Java and .NET applications. He also discussed the technologies that provide distributed transactions using standards like WS-Atomic Transaction and WS-Coordination and direct bridging using a shared-memory, Java Virtual Machine (JVM)-to-CLR implementation.
Google's Daniel Peng and Frank Dabek published a paper on "Large-scale Incremental Processing Using Distributed Transactions and Notifications” explaining that databases do not meet the storage or throughput requirements for Google's indexing system which stores tens of petabytes of data and processes billions of updates per day on thousands of machines.
After several years of development, the developers from NeoTechnology have released version 1.0 of Neo4j, a Java-based graph database which follows the property graph datamodel. InfoQ spoke with NeoTechnology COO Peter Neubauer to learn more about the current Neo4j release and what it offers to developers.
JNBridge is a technology that allows Java and .NET code to share objects without relying on cross-compilers. Under this scheme, the JVM and CLR may be running on the separate machines, separate processes on the same machine, or even in the same process. With JNBridge 5.0, these capabilities have been extended to also support each platforms native transaction support.
Despite the extreme importance of transaction processing for ensuring reliability and manageability of distributed computing and several existing WS-* standards, the implementation of the transactional behavior in SOA is still pretty rare. The Reservation pattern, described in a new post by Arnon Rotem-Gal-Oz, provides one of the possible solutions to this problem.
Microsoft has released a new version of .NET 4.0 Beta 1, one that incorporates STM.NET, the Software Transactional Memory. STM is an alternative mechanism to lock-based synchronization used to control the concurrent access to shared memory.
The topic of distributed transactions and their place within a REST world has come up again recently. Many people have indicated that they are either thinking of using the combination or are doing so now. Others, including Roy Fielding, believe that the two simply do not go together.
.NET 4 will have new types to support building cancellation-aware applications and libraries. The new CancellationToken, CancellationTokenSource, and cancellation exception types provide a cooperative cancellation framework.