BT

Raffi Krikorian Provides Guidance for “Re-architecting on the Fly”

by Daniel Bryant on  Apr 06, 2015

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.

The Architecture of a Scalable and Resilient Google Cloud Solution

by Abel Avram on  Apr 03, 2015

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 Built by Microservices

by Jan Stenberg on  Mar 31, 2015

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.

5 Design Principles for System Configuration

by Manuel Pais on  Mar 25, 2015

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.

Clarifying Domain-Driven Design Using a Trading Application Example

by Jan Stenberg on  Mar 24, 2015

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.

Making Sense of Event Stream Processing

by Jan Stenberg on  Mar 22, 2015 1

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).

Lessons Learned From Scaling Services at Google and eBay

by João Miranda on  Mar 22, 2015

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.

Yelp Engineering: Using Services to Break Down a Monolith

by Daniel Bryant on  Mar 19, 2015

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.

Effektif Open Sources BPM Software with an Emphasis on Developers

by Victor Grazi on  Mar 16, 2015 2

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

Uber Unveils its Realtime Market Platform

by João Miranda on  Mar 15, 2015

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.

Phil Calcado on Lessons Learnt During SoundCloud's Microservice Migration

by Daniel Bryant on  Mar 15, 2015

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.

A Modern Microservices Architecture

by Jan Stenberg on  Mar 10, 2015

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.

Microservices Are Conceptually Too Big

by Jan Stenberg on  Mar 09, 2015 3

Microservices are conceptually too big; they conflate optimizing for organisational and technical factors, but solutions to problems of each type may not fit together very well, Phil Wills, senior architect at The Guardian, explained in a presentation at the QCon London conference promoting thinking about independent services and single responsibility applications, rather than microservices.

How Twitter Answers Handles Five Billion Sessions a Day

by Sergio De Simone on  Mar 09, 2015

Twitter's Answers is an analytics service for mobile apps that has come to see five billion sessions per day. Ed Solovey, software engineer at Twitter, has described how their system works to provide "reliable, real-time, and actionable" data based on hundreds of millions of mobile devices sending millions of events every second.

Microservices and the Goal of Software Development

by Jan Stenberg on  Mar 08, 2015

The goal of software is to sustainably minimize lead time to positive business impact, everything else is detail, Dan North claimed in a presentation at the QCon London conference describing ways of reasoning about code and how this leads him into an architecture style that may fit microservices.

General Feedback
Bugs
Advertising
Editorial
Marketing
InfoQ.com and all content copyright © 2006-2015 C4Media Inc. InfoQ.com hosted at Contegix, the best ISP we've ever worked with.
Privacy policy
BT