InfoQ Homepage Architecture Content on InfoQ
-
Netflix Play API: Building an Evolutionary Architecture
At QCon SF, Suudhan Rangarajan presented “Netflix Play API: Why We Built an Evolutionary Architecture”. Key takeaways included: services that have a single identity/responsibility are easier to upgrade; spend time identifying core decisions that need to be made when building a service; and designing an “evolutionary architecture” using tools like fitness functions provides many benefits.
-
Hyperledger Sawtooth 1.1 Adds New Consensus Algorithms and WebAssembly Smart Contracts
After the initial GA release back in February, the Hyperledger project has just released version 1.1 of Sawtooth, which mostly focuses on making it simpler to add new consensus algorithms and brings WebAssembly smart contracts.
-
Amazon Announces an AWS Well-Architected Tool to Review Workloads Against Best Practices
At the recent AWS re:Invent 2018 event, Amazon announced a new Well Architected tool - a self-service tool that helps customers review AWS workloads at any time without the need for an AWS Architect. Moreover, this new tool uses the AWS Well-Architect Framework launched back in 2015.
-
The Human Side of Microservices
A microservices architecture is a game changer for team communication, not a purely technical solution. If different teams don’t have stable, direct communication channels, the software they produce will suffer. The five key properties crucial for a successful microservices implementation are zero-configuration, auto-discovery, high redundancy, self-healing, and fault tolerance.
-
Building Production-Ready Applications: Michael Kehoe Shares Lessons Learned from LinkedIn
At QCon San Francisco, Michael Kehoe presented “Building Production-Ready Applications”. Drawing on his experience with site reliability engineering (SRE), he introduced the tenets of “production-readiness” that all engineers across the organisation should focus on as: stability and reliability; scalability and performance; fault tolerance and disaster recovery; monitoring; and documentation.
-
How Reddit Rewrote Their iOS App to Improve Performance, Modularity, and Testing
Reddit has been hard at work in the last year to improve the performance of their iOS app while also making it suitable for faster iteration cycles, improved test coverage, and better extensibility. All of this was made possible by evolving the app original MVC architecture into a Model-View-Presenter (MVP) architecture.
-
Vaughn Vernon: The Reality of Being Cloud-Native and Reactive
Reactive, Streaming and NoSQL are important concepts today and can be very useful, and sometimes considered compulsory for cloud-native applications, but Vaughn Vernon emphasizes in a blog post that not all systems within in a company must use all these concepts to achieve the full benefits of the cloud.
-
QCon New York 2018: What the Speakers Will Be Watching
The 7th Annual QCon New York is just a week away. A major theme for this year's conference is around successful lessons operating, managing, and debugging Microservice environments from companies like Google, Shopify, Square, IBM, Github, and Lyft.
-
How Technical Practices Support Evolutionary Architecture and Continuous Delivery
Technical practices of XP such as TDD, Refactoring, CI and Pair Programming support emergent design and enable evolving your architecture. The first practice you need for continuous delivery is CI, committing to mainline every day. Being able to write clean, well-factored, and well-tested modular code is the most important skill for developers.
-
SkyWalking Accepted by Apache Software Foundation as an Incubator Project
SkyWalking's proposal into the Incubator has been voted on and accepted by Apache Software Foundation(ASF) IPMC. SkyWalking is an APM (application performance monitor) tool, especially designed for microservices, cloud-native and container-based architectures. SkyWalking’s underlying technology is a distributed tracing system.
-
Werner Vogels on “21st Century [Cloud] Architectures”: Availability, Reliability and Resilience
At the AWS re:invent 2017 conference, Werner Vogels, CTO of Amazon, presented a keynote that discussed core concepts required for building “21st Century Architectures” on the cloud. Highlights of the talk included discussion of the emerging practices of evolutionary and “cloud native” architectures, the role of security becoming everyone’s responsibility, and the benefits of chaos engineering.
-
Adrian Cockcroft Discusses Chaos Architecture: "Four Layers, Two Teams, and an Attitude"
At QCon San Francisco, Adrian Cockcroft presented “Chaos Architecture”, and discussed the evolution of cloud native architecture, and how chaos engineering can be applied to produce better and safer systems. Effective chaos architecture and engineering was presented as consisting of “four layers, two teams, and an attitude”.
-
Android Architecture Components 1.0: Lifecycle, LiveData, ViewModel and Room
Google has made available Android Architecture Components 1.0, a collection of libraries to design “robust, testable, and maintainable apps.” The current components are Lifecycle, LiveData, ViewModel and Room with others on the way.
-
Tracks Announced for the Inaugural QCon.ai in 2018
Recently, the people behind QCon (InfoQ’s conference for senior developers, architects, and leaders in software) announced a new conference called QCon.ai.
-
Monzo Outage Post Mortem
Monzo, the digital, mobile-only bank based in the UK, recently suffered outages in their current account payments and prepaid debit cards systems. Oliver Beattie, Monzo’s head of engineering, took on Monzo’s community forum to provide a post mortem of the outage. In this article, we describe their architecture, the root cause of the outage and the lessons learned from it.