InfoQ Homepage Articles
-
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.
-
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.
-
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.
-
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.
-
Leadership & Effective Communication - Panel Discussion
InfoQ spoke to several technical leaders to understand how they adapt their communication strategies for the current challenges in the distributed and technology-driven workplaces.
-
Helidon 4 Adopts Virtual Threads: Explore the Increased Performance and Improved DevEx
This article delves into Helidon 4's integration of Java 21's virtual threads from Project Loom, marking a significant shift in Java development. It highlights the transition from a reactive to an imperative model, simplifying coding and debugging. Helidon 4 claims improved performance over previous versions and some external frameworks, balancing performance with simplicity.
-
Navigating Complex Interpersonal Relationships: Co-Creating Deliberate Workplace Connection
As an employee or leader, you are in a relationship with each other and with the organization. You face the tension of traditional ways of working vs new ways of working in the call for more work-from-home policies, and more work/life balance. This article outlines the mindset and actions that can be taken to better navigate complex relationships leading to a more humanistic way of working.
-
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.
-
Adopting Asynchronous Collaboration in Distributed Software Teams
Meetings can be a major time-sink for distributed teams. While they can be valuable, if we reach for them as a default way of working, we inadvertently create a fragmented team calendar. This can be a drain on productivity, especially for knowledge workers who need time to focus on deep work. This article discusses the benefits of asynchronous collaboration and how to implement it on your team.