A process to build RESTful APIs that solve users’ needs with simplicity, reliability, and performance.
This chapter from Cloud Native Java explores the constantly evolving way applications are built.
Architectural change is often connected to a desire for mastery, purpose, and autonomy.
Embrace plurality over single systems of record.
What you need to consider when your microservices architecture is tightly coupled.
Explore essential components, principles, and key metrics.
Define and maintain a state machine within an object-oriented software system.
Open source software is everywhere, but do you know where to start if you want to contribute, convince your manager your next project should be open source, or avoid recreating the wheel?
This chapter from Learning Agile lays out the 12 principles that every agile practitioner should use when working on a software project team.
Learn how to build scalable, adaptive, complex systems that help your business adjust to rapidly changing competitive markets.
Become familiar with various ways to design technical methods that minimize the risk of having a class of users who must be trusted—of their own volition—to behave within a set of rules in order to safeguard privacy.
How New Relic increases system stability and manages growth without going off the rails.
Markus Eisele walks you through the creation of a complete reactive microservices-based system.
Examine the benefits of microservice architecture and techniques to achieve them.
Learn how to configure and automate API caching for maximum performance and broad protection.
Properly organizing information is essential, but it can be hard to know where to start. Learn the fundamental building blocks of a modern information architecture.
Adrian Cockcroft explores the key aspects of large-scale microservice deployments that tend to be skipped.
Learn the core differences between microservices and SOA so you can make an informed choice when determining which is best for your particular situation.
Russell Pavlicek reviews unikernel systems and considers how microservices built on highly secure unikernels can remake the principles of solution architecture.
Robert Hurlbut offers practical strategies for threat modeling for secure software design and explains how to apply risk management to deal with the threats.
David Strauss explores methods for maintaining agility and security in distributed and microservice architectures.
Public transport systems are good examples of complex systems that operate on many different levels. By examining public transport systems and their histories, we can spot familiar topics that are relevant to the building of software architectures.
Take a deep dive through the evolution of the if(we) data science architecture.
As we move toward architectures designed to cope with changing requirements, how can we manage change in a secure way? Michael Brunton-Spall's tutorial digs into that question.
In this tutorial, discover the three main strategies for dealing with partial failures in distributed systems: using idempotent service interfaces; placing service boundaries between optional or less-critical functionality; and recombining services.
Sean Leach from Fastly examines traffic replays of a web attack, what the attacker was targeting, and the technologies that were used to block the attack in this video from Software Architecture 2015.
Mark Richards focuses on the essential soft skills of architecture, including working with architecture teams, leadership skills, leveraging checklists, negotiation skills, and facilitation skills.
Security mistakes tend to make headlines. In this segment from "Modeling for Software Architects," explore a model that can help you understand your security needs and keep your company out of the news.
"Building Microservices" takes a holistic view of the topics that system architects and administrators must consider when building, managing, and evolving microservice architectures. In this excerpt, you'll take a look at testing.
Zookeeper is a distributed in-memory database that sits at the heart of many open-source distributed systems. In this segment of "Distributed Systems in One Lesson," we look at Zookeeper's data model and explore some common uses cases.
Using the wrong architecture pattern (or no pattern at all) can be a very costly mistake.
For the beginner architect, there are many options for doing pretty much anything. But for the Master architect, there are only a few.
An exploration of what happens with storage, computation, and coordination between servers in a distributed system.