In a recent article on Medium, TypeSafe's Kevin Webber argues that reactive programming "isn’t just another trend but rather the paradigm for modern software developers to learn" since it helps them to build systems that are responsive, resilient, and scalable. He also suggests that actor-based concurrency is the most convenient foundations for a reactive system.
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.
Google has unveiled their new data-warehouse called Mesa. Mesa is a system that scales across multiple data centers and processes petabytes of data, while being able to respond to queries in sub-second time and maintain ACID properties.
Last week Vaughn Vernon published Dotsero, a .NET actor model toolkit that follows the Akka API and earlier this year a preview of the Orleans framework based on the Actor model was released by Microsoft Research. In a recent twitter discussion Vaughn and Sergey Bykov, lead of the Orleans project at Microsoft Research, discussed the different approaches taken in Orleans and Dotsero.
Causal Consistency models offer an alternative Eventual Consistency for distributed systems; both models should be weighed against your system's requirements and risk tolerance.
This article has been updated based on community and Jing Chen (Facebook)’s reaction. (See the Update section below.) Facebook came to the conclusion that MVC does not scale up for their needs and has decided to use a different pattern instead: Flux.
Facebook, Google, LinkedIn, and Twitter have decided to make sure that a relational databases is “web-scale”, so they have put their efforts behind WebScaleSQL, a branch of MySQL 5.6 Community Edition.
HybridCluster have announced a free for non-commercial use license for their cloud hosting platform. The platform supports Linux, Apache, MySQL and PHP (LAMP) applications, and provides high availability and auto scaling with a combination of ‘AwesomeProxy’ a proprietary multi-protocol proxy server, lightweight containers and a ZFS based storage fabric.
Being clever about system architecture in advance is hard. Scaling successfully is more about being clever with metrics and introspection, creating efficient build and provisioning processes and being comfortable with radical change. These are some of the keys to scaling at Dropbox according to Rajiv Eranki in his recent presentation at the 2013 RAMP Conference.
Oracle has published MySQL Reference Architectures for Massively Scalable Web Infrastructure, a whitepaper outlining recommended topologies for different types and sizes of websites using MySQL for data storage.
Christopher Smith shared insight into approaching and solving the problems of scaling web applications in his presentation "The Five Stages of Scale" at Scale11x last month. In Christopher's presentation he made a case for approaching scaling in a stages with well defined components that are either added or optimized to improve the overall scale of a web application.
Opscode released Chef 11 early this month with enhancements to its scalability to meet the demands of hyperscale web operations. Opscode rewrote the entire server core API in Erlang and at the same time kept it backward compatible. Opscode renamed the core server API "Erchef" to complement the rewrite in Erlang.
Mozilla is scaling websites from thousands to hundreds of millions of users through simple scaling patterns they have learned internally according to Brandon Burton, web operations engineer at Mozilla. The lessons learned include caching, scaling out web servers, asynchronous jobs, and databases.
Chinese Ecommerce Giant, Alibaba, recently managed to sell $3 billion worth of product in a single 24 hour period. InfoQ got a chance to ask a few questions to Zhuang Zhuoran and Youtan, architects from Tmall and Taobao, about the challenges of handling such loads and how they meet them.
Another AWS outage hit several large websites and their services last week. What can be done to avoid downtime? Architect for failover not just for scale.