InfoQ Homepage Articles
-
/articles/mva-enough-architecture/en/smallimage/balancing-mva-vs-mvp--small-logo-1705941964058.jpg)
How Much Architecture Is “Enough?”: Balancing the MVP and MVA Helps You Make Better Decisions
The Minimum Viable Architecture (MVA) is the architectural complement to a Minimum Viable Product (MVP). The MVA and MVP must evolve together for a product to be successful. As new features are delivered to customers, corresponding incremental improvements need to be made in the architecture. Also, the architecture should not get too far ahead of what is needed for the product.
-
/articles/ai-organizational-resilience/en/smallimage/generative-AI-and-organizational-resilience-small-1705597161955.jpg)
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.
-
/articles/cloud-computing-post-serverless-trends/en/smallimage/cloud-computing-in-the-post-serverless-era-small-1705591739195.jpg)
Cloud-Computing in the Post-Serverless Era: Current Trends and beyond
Discover the evolution of cloud-computing in the post-serverless era, with a shift towards hyper-specialized vertical multi-cloud services and a trend moving from Infrastructure as Code to Composition as Code. Microservices are being redefined in the cloud landscape and upcoming cloud services are set to be rich in constructs.
-
/articles/large-language-models-llms-prompting/en/smallimage/Maximizing-the-utility-of-large-language-models-through-prompting-small-1705424512331.jpg)
Maximizing the Utility of Large Language Models (LLMs) through Prompting
In this article, authors Numa Dhamani and Maggie Engler discuss how prompt engineering techniques can help use the large language models (LLMs) more effectively to achieve better results. Prompting techniques discussed include few-shot, chain-of-thought, self-consistency, and tree-of-thoughts prompting.
-
/articles/breaking-changes-are-broken-semver/en/smallimage/breaking-changes-are-broken-small-1705413989390.jpg)
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.
-
/articles/orchestrating-resilience-modern-asynchronous-systems/en/smallimage/orchestrating-resilience-building-modern-asynchronous-systems-small-1704800443421.jpg)
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.
-
/articles/incident-lifecycle-resilience/en/smallimage/incident-lifecycle-small-1704809120918.jpg)
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.
-
/articles/architecting-java-persistence-patterns-and-strategies/en/smallimage/small-image-1703761535339.jpg)
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.
-
/articles/staff-engineers-impact-incidents/en/smallimage/tips-for-how-staff-plus-engineers-can-impact-incidents-small-1703672685677.jpg)
Tips on How Staff Engineers Can Impact Incidents
Staff engineers can influence behaviors during and after incidents by modeling transparency and questioning assumptions to strengthen engineering culture. As incident commanders, they can coordinate workstreams, communicate with stakeholders, and prevent responder burnout. In retrospectives, staff engineers can improve model root cause analysis to improve underlying cultural issues.
-
/articles/risk-first-compliance/en/smallimage/from-compliance-first-to-risk-first-small-1703233223207.jpg)
From Compliance-First to Risk-First: Why Companies Need a Culture Shift
Transitioning from a "Compliancе-First" approach to a "Risk-First" mindset rеcognizеs that compliancе should not be viеwеd in isolation, but as a componеnt of a broadеr risk managеmеnt strategy.
-
/articles/organizational-resilience-documentation/en/smallimage/building-organizational-resilience-through-documentation-and-InnerSource-small-1702890930736.jpg)
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.
-
/articles/avoid-architecture-pitfalls/en/smallimage/12-software-architecture-pitfalls-and-how-to-avoid-them-small-1702296085274.jpg)
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.