InfoQ Homepage Architecture Content on InfoQ
-
Architecture with 800 of My Closest Friends: The Evolution of Comcast’s Architecture Guild
Comcast has cultivated an Architecture Guild, with the goal of "threading the needle" between obtaining advantageous critical mass around certain common technologies without undermining individual teams' agency. The Architecture Guild is a grassroots framework that has been used to cut across organizational boundaries to identify solid, workable, default recommendations.
-
The Potential for Using a Service Mesh for Event-Driven Messaging
In this article, we discuss one of the most challenging and unexplored areas in service mesh architecture; supporting event-driven messaging. There are two main architectural patterns that we discuss here: the protocol proxy sidecar, and the HTTP bridge sidecar. Regardless of the pattern that is used, the sidecar can facilitate features such as observability, throttling, tracing etc.
-
API Gateways and Service Meshes: Opening the Door to Application Modernisation
Modernising applications by decoupling them from the underlying infrastructure on which they are running can enable innovation, reduce costs, and improve security. An API Gateway can decouple applications from external consumers, and a service mesh decouples applications from internal consumers.
-
The Many Flavors of “Low-Code”
While the low-code hype often tells how "citizen developers" can create enterprise applications without the need to code, these platforms can serve an important role for professional developers.
-
Robust Engineering: User Interfaces You Can Trust with State Machines
Industrial-strength modelling techniques used in safety-critical domains can be leveraged for the specification and implementation of user interfaces. This article explains how state machine modelling may lead to robust, testable and maintainable user interfaces.
-
To Multicluster, or Not to Multicluster: Inter-Cluster Communication Using a Service Mesh
Communication within Kubernetes clusters is a solved issue, but communication across clusters requires more design and operational overhead. Before deciding on whether to implement multicluster support, you should understand your communication use case.
-
Key Takeaway Points and Lessons Learned from QCon London 2019
QCon returned to London this past March for its thirteenth year in the city, attracting 1,500 senior developers, architects, and team leads.
-
Bots Are Coming! Approaches for Testing Conversational Interfaces
Voice-based computing interfaces need testing with an adapted approached, suited for their specificity and context. Some things need to be adapted (test strategy, testing approach, validation criteria), while others can be re-used (e.g. API testing approaches and tools), and some require learning new things (e.g. testing artificial intelligence models and components).
-
Q&A on the Book What’s Your Digital Business Model
The book What’s Your Digital Business Model, by Peter Weill and Stephanie L. Woerner, explores how companies can reinvent themselves to become successful in the digital economy. It provides a research-based framework, coupled with assessments and examples, for executives to think about how to compete in the digital era and decide what’s needed to migrate towards a digital business model.
-
Linkerd v2: How Lessons from Production Adoption Resulted in a Rewrite of the Service Mesh
Linkerd 2.0 introduced a substantial rewrite of the widely adopted service mesh, using a split between Go and Rust. In this article, we discuss the lessons learned in the "cauldron of production adoption", and how those lessons became the basis of Linkerd 2.x’s philosophy, design, and implementation.
-
Scrum@Scale: An Interview with Agile Manifesto Co-Author and Scrum Co-Founder Jeff Sutherland
Jeff Sutherland founded Scrum@Scale to help organizations address critical scaling challenges. Leaders form an Executive Action Team and are responsible for addressing organizational impediments.
-
Transforming the Healthcare Industry through API Marketplaces
A key problem in the healthcare industry is that valuable data points are hidden and siloed. Through an API marketplace, we can expose these data points securely and make them accessible by healthcare industry stakeholders and citizens alike, improving efficiency in the industry and enabling innovation in population health technologies.