Recently Adrian Cockcroft gave an interview to ActiveState's John Wetherill about microservices. In it he talks about how polyglot fits into microservices and the impact on him when he head that companies such as Target and Macy's, as well as Homeland Security had adopted that architectural approach.
AnyPresence, one of the leading MBaaS players has launched JustAPIs, a platform for building and deploying RESTful APIs.
After three developer previews, six release candidates and over 1500 closed tickets the Apache foundation has announced version 1.0 of Apache HBase, a NoSQL database in the Hadoop ecosystem. After more than 7 years of active development, the team behind HBase felt that the project had matured and stabilized enough to warrant a 1.0 version.
At the inaugural O’Reilly Software Architecture conference, Raffi Krikorian discussed strategies and tactics for technical leads and architects who are undertaking a system rewrite. Drawing on his experience as VP of Twitter Engineering, Krikorian discussed a twelve point plan for managing a re-architecting, including defining “done”, instrumenting existing systems, and enforcing code quality.
Google has recently published a paper providing architectural guidelines for creating a scalable and resilient solution running on their cloud platform. This article digests the respective paper extracting the main ideas and advice. These guidelines can be used with minor changes for deploying web applications on other clouds.
A service is a logical construct owning a business capability and made up of internal autonomous components or microservices that together fulfil the responsibilities of the service, Jeppe Cramon suggests continuing a previous series of blog posts clarifying his view on building services around business capabilities and bounded contexts.
Popular configuration mechanisms like conf.d pose multiple problems when trying to converge system configuration using configuration management tools. Ish-Shalom proposes five design principles for configuration that prevent those problems. The core ideas being the use of a configuration API and the separation of configurations based on the type of system updates they require.
Domain-Driven Design (DDD) is an approach to building software emphasizing collaboration between domain experts, developers and others involved in order to meet business objectives, Naresh Bhatia explains introducing the DDD base concepts exemplifying with Bullsfirst, an example system of medium complexity from the financial trading domain.
Structuring data as a stream of events is an idea appearing in many areas and is the ideal way of storing data. Aggregating a read model from these events is an ideal way to present data to a user, Martin Kleppmann claims explains when describing the fundamental ideas behind Stream Processing, Event Sourcing and Complex Event Processing (CEP).
Randy Shoup shared his experiences to the QCon London audience in scaling services at Google and eBay, giving advice on building and operating services. A successful services strategy requires end-to-end service ownership, decentralized decision-making and standardization efforts focused on protocols of communications and supporting infrastructure.
The Yelp engineering team have stated that moving to a service-oriented architecture has allowed them to scale their development process and maintain a rapid pace of software delivery as the team and codebase has grown. This has been achieved by focusing on distributed systems education, creating a set of basic service design principles and implementing a supporting infrastructure.
Business process management software provider Effektif today announced the open sourcing of their workflow engine. The new model allows developers to include Effektif workflows from within their applications via Java and REST APIs
Matt Ranney, Chief Systems Architect at Uber, gave an overview of their dispatch system, responsible for matching Uber's drivers and riders. Ranney explained the driving forces that led to a rewrite of this system. He described the architectural principles that underpin it, several of the algorithms implemented and why Uber decided to design and implement their own RPC protocol.
At QCon London 2015 Phil Calcado shared lessons learnt from SoundCloud’s move from a monolithic to microservices architecture, and stated that the core requirements for building a microservice platform include developing capabilities for rapid provisioning, basic monitoring and rapid application deployment.
After living with microservices for three years at Gilt we can see advantages in team ownership, boundaries defined by APIs and complex problems broken down. Challenges still exists in tooling, integration environments and monitoring, Yoni Goldberg explained in a presentation at the QCon London conference describing the challenges they encountered moving to a microservices architecture.