Stripe, the internet payments infrastructure company recently announced open sourcing a set of internally developed tools based on Apache Hadoop.Timberlake, Brushfire, Sequins and Herringbone all contribute to enriching the available tools for building an Apache Hadoop stack.
Mark Nottingham, chair of the HTTP Working Group, asks the question What is the Web? As he mentions, this simple question has some complex and perhaps unexpected answers depending upon your perspective. A common approach would be to say that it has to be rooted in the Web browser, but that has some interesting consequences, not all of which are useful for non-browser stakeholders.
GridGain's In-Memory Data Fabric entered Apache Incubator last October under the name of Apache Ignite. The company donated its flagship in-memory computing platform to the Apache Software Foundation with the intention of attracting external developers and growing a viable community around its core technology.
At the StrataHadoop conference in Barcelona last week, Rod Smith, Vice President of the IBM Emerging Internet Technologies organization, presented work on an internal product they have been developing in their consulting work with clients that integrates data sources, and data analysis.
Microservices are not new ideas and we will over the course of 3-5 years end up rebuilding WS-* the same way Web Services did rebuild all from CORBA unless we learn from our mistakes and improve to prevent them from being made again, Greg Young stated in a presentation at the Microservices Conference in London.
Microservices are valuable, but to break things up properly creating the right boundaries we need to understand our business and its processes Jeppe Cramon stated in a presentation at the Microservices Conference in London.
Udi Dahan describes how looking for highly cohesive, loosely coupled microservices, not within a system but over the enterprise, we can end up with a focus on organising services around business capabilities spanning the whole organisation since this is what the business care about.
Anne Thomas has summarized in a webinar the shift from large applications to small focused apps relying on services, while Matias Duarte has spoken in an interview about connecting these apps.
When working with Microservices pushing them to the cloud, people often find it difficult to understand the new architecture, it’s a paradigm shift, Daniel Bryant explains in a presentation at the Microservices Conference in London. As a help when designing and implementing cloud microservices Daniel has created the DHARMA principles, the idea being to use them as a checklist.
Databricks has recently announced a new record in the Daytona GraySort contest using the Spark processing engine. The Daytona GraySort contest is a 3rd party benchmark measuring how fast a system can sort 100 Terabytes of data. Databricks posted a throughput of 4.27 TB/min over a cluster of 206 machines for their official run.
When using Domain-Driven Design (DDD) separating the concerns of a large system into bounded contexts with each context using its own data store there is often a need to share some common data. One way of doing that is to let each context publish events about changes, events that others can listen to, Julie Lerman recently explained in MSDN Magazine.
This post describes the relation of Agility and Modularity. Why modularity is important and how can we use it is described in OSGi white paper.
A common context for Command-Query Responsibility Segregation (CQRS) is a collaborative domain with multiple users working on the same set of data, it is less suitable in domains with only a single user working on a piece of data, Udi Dahan explained when discussing CQRS in an interview.
Hortonworks Data Platform (HDP) version 2.2 with features based around Hadoop and YARN has better support for enterprise features such as security, compliance and so on as well.
Microsoft recently published a case study describing how a massively multiplayer online (MMO) game used Microsoft Azure to support tens of thousands of players in a single space battle. The case study looks at how architectural considerations like connectivity, latency, and scale can be addressed in an elastic cloud environment that must respond quickly to unexpected bursts in demand.