A little over a year ago I wrote a post about Roslyn. Recently (after seeing Mads Torgersen's excellent NDC-london talk) I was inspired to attempt to write my own mini-C# compiler to address some o...
Reactive Extensions (Rx) – Part 1 – Replacing C# Events Reactive Extensions (Rx) – Part 2 – Wrapping C# Events Reactive Extensions (Rx) – Part 3 – Naming Conventions For those who have not tried Reactive Extensions (Rx) yet, I highly recommend it. If I had to describe it in a few words it would(...)
In Next gen NoSQL: The demise of eventual consistency a recent post on Gigaom FoundationDB founder Dave Rosenthal proclaims the demise of eventual consistency. He argues that Google Spanner “demonstrates the falsity of a trade-off between strong consistency and high availability”. In this article I show that Google Spanner does not disprove CAP, but rather chooses one of many possible compromises between total consistency and total availability. For organizations with a less potent infrastructure than Google other compromises might be more suitable, and therefore eventual consistency is still a very good idea, even for future generations of nosql databases. Dave’s article brings up a good and interesting discussion. However I believe that in the end he misses the point. At the end he talks about machines failing and clients no longer being able to talk with those machines. Well, that is obvious. But a partition is a failure that is very different from a machine failing. Nobody has problems with consistency when a machine fails. A partition is a network connection failure such that on either side of the failed network connection are both clients and database servers. I will try to show that there still is a real and important consideration in this situation (which is at the core of the CAP theorem). And I will try to demonstrate this with an example. So, assume Nozama is a large web shop. It has a database with all the products, containing – among other information – for each product the number of items in stock. When a customer orders a product the system checks whether there are still items left in stock, and if so reserves one item for this customer and reduces the number of items in stock accordingly. Reliability is very important for Nozama, and so they have their servers in two computing centres, one in Europe and one in the USA. Customers in Europe are connected to the computing centre in Europe and customers in the USA are connected to the computing centre in the USA. In this context availability means that all customers (in Europe and the USA) can order any product at any time (as long as it is in stock). I.e. the only reason why the website would tell the customer that she cannot order a particular product is because no items are in stock for this product. And consistency means that all customersaaa
Pieter Hintjens explains the basic techniques for building very large distributed systems using fast asynchronous messaging in general, and ZeroMQ specifically.
To get content containing either thought or leadership enter:
To get content containing both thought and leadership enter:
To get content containing the expression thought leadership enter:
You can enter several keywords and you can refine them whenever you want. Our suggestion engine uses more signals but entering a few keywords here will rapidly give you great content to curate.