InfoQ Homepage Architecture Content on InfoQ
-
Generative AI and Organizational Resilience
Generative AI will profoundly transform communication and information sharing over the next decade, but the change will be uneven across industries and roles. Organizations should empower workers to use AI augmentation thoughtfully, while building literacy on capabilities and limits. A balanced, conscientious integration, using iterations and customer feedback, will produce the best outcomes.
-
Beyond API Compatibility: Understanding the Full Impact of Breaking Changes
In this article, we address the most contentious and misinterpreted parts of the SemVer standard, i.e backward compatibility and breaking changes. With the proliferation of SaaS APIs for Generative AI continuing, now is a good time for a retrospection on what constitutes a breaking change and how you can trade off backward compatibility and upgradability with modernization and iterability.
-
Orchestrating Resilience Building Modern Asynchronous Systems
In this article, we will discuss what problems we had to solve at Twilio to efficiently build a resilient and scalable asynchronous system to handle a complex workflow and the advantages we got from adopting a Workflow Orchestration solution, including abstracting away state management and out-of-the-box support for retries, observability, and audibility.
-
The Incident Lifecycle: How a Culture of Resilience Can Help You Accomplish Your Goals
Don’t get stuck with overwhelmed systems that can cause an outage, like what happened with Taylor Swift concert tickets. Build organizational resilience to incidents through improved coordination and communication during the response, and blameless reviews, root cause analysis, and insightful communication afterward to enable meaningful change.
-
Architecting with Java Persistence: Patterns and Strategies
Explore a spectrum of Java persistence patterns, from data-oriented to domain-centric. Delve into Driver, Mapper, DAO, Active Record, and Repository for robust architectural foundations.
-
Write More, Talk Less: Building Organizational Resilience through Documentation and InnerSource
Better documentation and knowledge sharing creates transparency that aids onboarding, prevents turnover disruption, and withstands reorganizations. Different practices can help, such as communicating asynchronously, creating incentives for documentation, making docs discoverable, understanding team members' preferences, and providing dedicated writing time. And maybe InnerSource can help too.
-
12 Software Architecture Pitfalls and How to Avoid Them
Knowing about potential software architecture pitfalls can help teams by keeping them away from tempting paths that will not take them where they want to go. This article covers some of those pitfalls, and provides guidance on how they can be avoided.
-
Going Global: a Deep Dive to Build an Internationalization Framework
Internationalization (i18n) is a critical process in web development, and requires a robust, well-designed framework to ensure scalability. While some JavaScript libraries exist, this article provides a language-agonistic framework that can be implemented at a global level.
-
From Dependency to Autonomy: Building an In-House E-signing Service
While many companies rely on third-party services, there’s a growing realization that an in-house solution can offer more control, flexibility, and cost savings. In this article, we’ll delve into how to build an e-signing microservice.
-
The False Dichotomy of Monolith vs. Microservices
Taking sides in the debate of microservices v. monolith gets in the way of doing the right thing for our customers. Sometimes, we need microservices. Sometimes, we need a monolith. Most of the time we are better off somewhere between these extremes.
-
Has Your Architectural Decision Record Lost Its Purpose?
Architectural Decision Records (ADRs) are important vehicles for communicating the architectural decisions a development team makes about a system. Lacking a clear definition of what is architectural, and also lacking anywhere else to record important decisions, they can start to drift from their original purpose and lose focus and effectiveness.
-
How Agile Teams Can Improve Predictability by Measuring Stability
In this article, we will present our approach for analysing agile systems as networks of queues and how we have used it to analyse 926 projects in the Public Jira Dataset. We explain how you can measure the Stability Metric (SM) for your queues. Finally, we will present our planned next phase of research.