Machine learning is taking the world by storm, and many companies with rules engines in place for making business decisions are starting to leverage it. However, the two technologies are geared toward different problems. Andrew Bonham details the strengths of both rules engines and machine learning and identifies the best use cases for each.
Mark Richards challenges some of the tried-and-true axioms in software architecture and shows you how to manage the ever-changing state of software architecture.
The engineers on the New York Times digital games team bake quality into every new product and feature they deliver. Join Phil Wells for an overview of how the team builds a culture of quality. You'll discover a few of the technical tools and tricks the team uses to ensure confidence and velocity in their software delivery process.
Maggie Carroll teaches you how to develop influence through relationship building and a tool for moving from a fire-fighting mode to proactive ownership, which she created as an enterprise architect. She also shares useful skills and actionable techniques for creating a new enterprise architecture function and a tool for remaining productive as a leader.
As applications have increased in complexity, so have the queries needed to understand the state and performance of those systems, leading to an explosion in the volume and dimensionality of metrics. Joel Barciauskas outlines how Datadog architected its pipelines, data structures, and storage engines to answer these complex questions, all while scaling to ingest trillions of points per day.
Services can expose sensitive data. However, we often "secure" these services using an API key or security through obscurity. James Wallace explains what you need to secure and how to secure it and shares solutions that can be implemented for both server- and client-side requests—so no matter what your services expose, you'll understand how to build secure distributed architectures.
The New York Times sends nearly 4 billion emails per year and push notifications to 50 million devices. Recently, the messaging team replatformed the entire service that supports emails and push notifications. Katerina Iliakopoulou shares the journey from retiring the legacy systems used for sending emails and push notifications at the Times to a new, stable, and highly scalable platform.
John Chapin explains how—in this brave new world of managed services and platforms—you can use serverless technologies and an infrastructure-as-code mind-set to architect, build, and operate resilient systems that survive even massive vendor outages.
Nubank is a national bank from Brazil with 12 million customers and an architecture with 300+ microservices that are totally cloud based. Luiz Hespanha and Lucas Cavalcanti outline the challenges of expanding to other countries and internationalizing all the bank's services.
In his time designing and deploying large-scale data lakes and distributed systems, Jesus Jackson has learned many hard truths and discovered many myths. Join in to hear some of these myths, lessons learned, and war stories.
Mike Amundsen explains the important balance between designing, building, and releasing APIs. You'll learn how to create a consistent process for your company to ensure your API teams produce quality APIs that developers can easily use to provide timely business solutions for your organization.
Digital transformation means adapting an organization's strategy and structure to capture opportunities enabled by digital technology. APIs are the connective fabric that's essential as a foundation for digital transformation. Erik Wilde explains why having an API strategy and executing it through an API program is a good way to get the most out of your digital transformation initiatives.
In this ongoing series, Neal Ford interviews highly regarded industry professionals about their career path and their work as an architect. Join us for his discussion with Rachel Laycock.
Micro-frontends are starting to get more traction thanks to the benefits they provide, like independent deployments, team autonomy, and a quick path to production. Luca Mezzalira illustrates how to structure a micro-frontend architecture and busts myths by providing concrete examples applied in the real world.
The path to growing innovation projects to highly scalable, resilient, and performant systems is riddled with challenges and doubts. Cristina Turbatu draws on her experience to highlight the problems that occur during the rapid evolution of proof-of-concept architectures to production-ready products while discussing some of the solutions to ongoing uncertainty and constant pivots.
Software today is staggeringly larger than the programs of the 1960s. George Fairbanks interrogates whether that means it's under our intellectual control or if we found ways to make progress without Edsger Dijkstra's high standards.
Rob Cameron and Lisa-Marie Namphy explain how containers are keeping your kids happy. Roblox maintains availability and performance of a platform used by over 90 million gamers each month. Kids and teens all over the world create the games, and little did they know, they're all container experts. (Or at least, their games are in good hands because of containers.)
Since the mid-1980s, relational databases have been standard for most applications to store and query structured data. As architectures became more complex, databases generalized to fit a variety of use cases. Simplicity was key: storage, indexing, caching, querying, and transaction management, all under a unified SQL. Alex Silva examines how relational databases overcome these challenges.
When you balance emergent changes created by Agile teams with strategic intentional architecture, you can foster a sustainable ecosystem in a mature (post–startup phase) organization. Nimisha Asthagiri shares her experiences bringing an organically built monolithic open source system to a more intentionally maintained platform using leading architectural principles and practices.
Software metrics can be used effectively to judge the maintainability and architectural quality of a code base. Even more importantly, they can be used as canaries in a coal mine to warn early about dangerous accumulations of architectural and technical debt.
Mike Amundsen demonstrates how to use the STAR method (stabilize, transform, add, and repeat) to safely and effectively migrate your existing IT infrastructure to a microservice platform—all without interrupting your current IT services.
Mark Richards outlines patterns for migrating monolithic and service-oriented architectures to microservices.
Steven Jones and Nicholas Fong walk you through migrating a chatbot, cognitive search, and other services to a Kubernetes-based architecture. Technologies include multiregion clusters, load balancers, integrating Express and Flask servers, and high-speed data transfer for importing models.
Join Scott Davis to explore W3C specifications like the Web Speech API (for speech synthesis and speech recognition), Speech Synthesis Markup Language (SSML), and WebVTT (for closed captioning). These technologies not only power smart speakers from Amazon, Google, Microsoft, and Apple; they power smartphones and desktop browsers as well.
Often microservices and bounded contexts are considered the same thing. They aren't. Vladik Khononov points out the difference between the two, provides heuristics for when each pattern should be used, and shares his experience optimizing microservices-based architectures at NaXex.
Patterns are an excellent way of building knowledge of an architectural style. And as serverless starts to mature, we start to see patterns emerge. Mike Roberts introduces you to some of these patterns and helps you look for them in your own organizations.
Adopting a microservices architecture can present new challenges in observability, networking, and security. Megan O'Keefe explores how Istio, an open source service mesh tool, can help you solve these challenges by providing a unified management layer for your services. Through demos, you'll learn how to use Istio to route traffic, automate security policies, and monitor services at scale.
We're all familiar with the title software architect, but you may not know what a software architect does or how to become one. Perhaps someone even gave you the title, but you're not sure what’s expected of you. Or you suspect you might be doing a job of a software architect, but can’t pinpoint when or explain how you made the leap. Join Sonya Natanzon to explore the role in depth.
As the use of cloud expands from initial use cases to broader consumption, new interdisciplinary interlock across software development, cloud architecture, and data architecture are required. In this keynote, we'll touch on key pain points of this inter-disciplinary era and look at the view of holistic cloud architecture and development.
Being a developer in today’s world means living and breathing technology, whether it's designing new systems or critiquing the design of your doctor’s scheduling web app (if they have one, that is). In the few moments in between, there isn’t time for much else. Sometimes Kai Holnes draws; sometimes she writes. What do you do?
Technical debt is a funny thing. It's the name we give engineering decisions we disagree with. Robert (r0ml) Lefkowitz leads a deep dive into technical debt—what it is, how to prevent it, and how to reduce it.
Upfront architecture is essential to ensure reliability. Ideally, the system design starts with defining clear service-level objectives (SLOs) that translate into the right architecture to avoid gold-plating or costly redesigns after the system is live. Marco van der Linden and Tom Hofte explain how to define clear SLOs and apply architectural patterns to design a system that works as promised.
In the many architectural assessments Martin Fowler's colleagues do in enterprises throughout the world, they commonly find one widely neglected architectural attribute. He doesn't claim that its identity will shock you, but it does fuel his venting for 20 minutes.
Amanda Kabak explains why there's more to stream processing than serverless workflows. Actors can provide the ability to create complex calculations meshes that run on cloud resources with cost-effective density.
Every 15 years or so, the common wisdom about the best architecture in the software world changes. Mary Poppendieck walks you through a few of the more dramatic architectural changes, looking at what triggered them and how well they worked out.
As engineers, we often find ourselves maintaining systems that are full of things outside our control but for which we're nevertheless held responsible. Big or small, these deep systems present significant engineering and operational challenges. Join Austin Parker to learn how to identify your deep systems—along with some techniques to manage them.