Making the case for architectural change
Architectural change is often connected to a desire for mastery, purpose, and autonomy.
Software Architecture
Observations on the changing discipline of software architecture.
Serverless architectures built on an open source platform
Daniel Krook explores Apache OpenWhisk on IBM Bluemix.
Implementing a reactive microservices system
An architectural overview of an image processing example.
Designing architecture in a complex system
Embrace plurality over single systems of record.
Avoid testing headaches with tightly coupled services
What you need to consider when your microservices architecture is tightly coupled.
Monitoring a production-ready microservice
Explore essential components, principles, and key metrics.
How to implement the state architectural pattern
Define and maintain a state machine within an object-oriented software system.
Design pressures lead to better code and better outcomes
An interview with Martin Thompson, High-Performance Computing Specialist at Real Logic.
A quick overview of serverless
Mike Roberts, co-founder at Symphonia, on how serverless came about, where it's being used, and what lies ahead.
Want to be a good software architect? Say “yes” to a lot of things.
An interview with Scott Shaw, Head of Technology, Australia, at ThoughtWorks.
How can a big enterprise benefit from microservices?
Making a lasting impact with microservices takes more than a change in technology.
Understanding reactive architecture through the actor model
The O’Reilly Podcast: Hugh McKee on learning how to think asynchronously to create highly concurrent business systems.
12 patterns for hypermedia service architecture
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?
12 Agile principles
This chapter from Learning Agile lays out the 12 principles that every agile practitioner should use when working on a software project team.
Microservices antipatterns and pitfalls
Author Mark Richards walks you through the 10 most common microservice anti-patterns and pitfalls, and provides solutions for avoiding them.
5 reasons to finally learn design patterns
Crafted by experienced object-oriented practitioners, design patterns can make your designs more flexible, more resilient to change, and easier to maintain.
Are microservices for you? You might be asking the wrong question.
Deciding whether to use microservices starts with understanding what isn’t working for you now.
Microservices for Java developers
Learn how to build scalable, adaptive, complex systems that help your business adjust to rapidly changing competitive markets.
Evolving architectures of FinTech
Learn how new FinTech architectures and startups are creating novel types of business models in Africa and Asia, where there are far fewer traditional banks, and in Europe and the US, where financial institutions generally avoid the market for small business loans.
Security architecture
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.
A biological and human approach to architecture: How New Relic builds to scale
How New Relic increases system stability and manages growth without going off the rails.
Developing reactive microservices
Markus Eisele walks you through the creation of a complete reactive microservices-based system.
The microservices value proposition
Examine the benefits of microservice architecture and techniques to achieve them.
API caching: Extending app architecture performance and security
Learn how to configure and automate API caching for maximum performance and broad protection.