InfoQ Homepage Architecture Content on InfoQ
-
Microservices Are Conceptually Too Big
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
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.
-
Your Code as a Crime Scene
Measuring software complexity is a popular and common activity among the software development community, judging by the number of tools built over the years and the literature around the subject. Drawing from his blend of engineering and psychology backgrounds, Adam Tornhill proposed to its audience at QCon London to treat their code as a crime scene, with the help of version control tools.
-
The Benefits of Microservices
Gene Kim (moderator), Gary Gruver, Andrew Phillips and Randy Shoup have discussed some of the benefits of microservices in a recent online panel.
-
An Architect's World View: A Guide to Values, Principles and Practices
At QCon London 2015, Colin Garlick presented “An Architect’s World View”, which provided a set of values, principles and practices to act as guidance for a software architect. The core values included people, the big picture, teamwork and integrity. Garlick proposed that these values are essentially characteristics that can be prioritised in order to work as a successful software architect.
-
Immutability Changes Everything Including Microservices
As computation and storage are cheap today, keeping immutable copies of lots of data becomes affordable, and by doing this, the coordination challenges can be reduced.
-
Using the "Worse is Better" Concept with Agile and Lean
Less functionality can make a better product according to the “Worse is Better” concept described 25 years ago by Richard P. Gabriel. According to Kevlin Henney and Frank Buschmann we can learn from the worse is better concept for development and architecture with agile and lean.
-
Application Architecture is Shifting towards Connected Apps
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.
-
Relation of Agility and Modularity
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.
-
Gregor Hohpe on Architects in Enterprises
Architecture is looking at things in a bigger context, thinking ahead and making decisions. Using their technical and communication skills architects can play a significant role in this by establishing direct contacts with people at different levels in an organisation, Gregor Hohpe said when sharing his experiences from working for Google, and now as Chief IT Architect at Allianz.
-
An Introduction to Minimum Viable Architecture
This post describes the minimum viable architecture for developing minimum viable product. It includes the architecture specification in different phases of startup.
-
Martin Fowler Describes "Sacrificial Architecture"
Martin Fowler describes Sacrificial Architecture. This post highlights the need and benefits of sacrificial Architecture.
-
Exploring the Hexagonal Architecture
Layered systems are an architectural style used essentially to avoid coupling, the biggest enemy of software maintainability, with Ports and Adapters, or a Hexagonal Architecture, an example of such an architecture, Ian Cooper explains in a presentation about architecture styles, specifically the Hexagonal Architecture.
-
Domain-Driven Design with Onion Architecture
Domain-Driven Design (DDD) together with Onion Architecture is a combination that Wade Waldron believes has increased his code quality dramatically since he started using it a few years back. Using DDD was a kick-off but together with Onion architecture he found his code to be more readable and understandable, and far easier to maintain.
-
Designing Systems for Testability
Testability must be explicitly designed in the system said Peter Zimmerer from Siemens AG. Test architects should drive testability and collaborate with architects, designers and testers in using good design and engineering practices. At the QA&Test 2014 conference Peter gave a tutorial about design for testability for embedded software systems.