InfoQ Homepage Architecture Content on InfoQ
-
Applying Flow Metrics to Design Resilient Microservices
Software design with resilience is an acknowledgement to the reality that everything fails. We put metrics in place to help us detect and resolve such problems and failures. Flow metrics, commonly used to measure how well teams deliver software, can be used to measure and improve system resilience.
-
Beyond Trends: A Practical Guide to Choosing the Right Message Broker
Choosing the right message broker for your application requires matching the appropriate technology with the messaging patterns needed. Message brokers can be broadly categorized as either stream-based or queue-based, each offering unique strengths and trade-offs.
-
Building Efficient Mobile Streaming Apps
This article explores efficient preloading systems for mobile video streaming apps, balancing user experience with technical constraints. We will dive into practical implementation strategies that leverage network intelligence, buffer management techniques, AI-driven preloading, and real-world testing methodologies to enhance video delivery in mobile environments.
-
If Architectural Experimentation Is So Great, Why Aren’t You Doing It?
Architectural experimentation sounds like a great idea, yet it does not seem to be used very frequently. In this article, we will explore some of the reasons why teams don’t use this powerful tool more often, and what they can do about leveraging that tool for successful outcomes.
-
2025 Article Contest: Win Your Conference Ticket
The InfoQ Team is excited to invite you to participate in our annual article writing competition. Authors of top-rated articles will win complimentary tickets to prominent software development conferences such as QCon and InfoQ Dev Summit.
-
The End of the Bronze Age: Rethinking the Medallion Architecture
A shift left approach to data processing relies on data products that form the basis of data communication across the business. This addresses many flaws in traditional data processing and makes data more relevant, complete, and trustworthy.
-
Software Architecture and the Art of Experimentation
Run experiments using a Minimum Viable Architecture approach to determine if your architecture decisions are on the right track. MVAs also test the viability of an MVP, allowing stakeholders to validate the business value.
-
Reaching Your Automatic Testing Goals by Enhancing Your Test Architecture
If you have automatic end-to-end tests, you have test architecture, even if you’ve never given it a thought. Test architecture encompasses everything from code to more theoretical concerns like enterprise architecture, but with concrete, immediate consequences. Let's explore how you can achieve the goals you have for your automatic testing effort.
-
Architectural Intelligence – the Next AI
Architectural Intelligence is the ability to look beyond AI hype and identify real AI components. Determining how, where, and when to use AI elements comes down to traditional trade-off analysis. Like any technology, AI can be used creatively, but inappropriately. Identify if AI makes sense for your use case, then work to use it effectively to meet your needs.
-
Reactive Real-Time Notifications with SSE, Spring Boot, and Redis Pub/Sub
Explore the power of reactive programming for building scalable real-time notification systems. Using Spring Boot Reactive and Spring WebFlux, leverage non-blocking operations to handle high-volume, asynchronous data flows efficiently. Discover how Redis Pub/Sub enables event-driven messaging and how the SSE protocol provides persistent connections for instant client updates without polling.
-
Transforming Legacy Healthcare Systems: a Journey to Cloud-Native Architecture
Discover how Livi navigated the complexities of transitioning MJog, a legacy healthcare system, to a cloud-native architecture, sharing valuable insights for successful tech modernization. Our experience illustrates that transitioning from legacy systems to cloud-based microservices is not a one-time project, but an ongoing journey.
-
To Dare or Not to Dare: the MVA Dilemma
Teams developing new products must decide between relying on tried-and-true technologies that may not be suitable for new situations or exploring new and unfamiliar technologies that may be a better fit but introduce unforeseen challenges.