InfoQ Homepage Articles
-
Platform Engineering Needs a Prescriptive Roadmap: a Conversation with Nigel Kersten
Nigel Kersten feels that it is time for a prescriptive roadmap for how to adopt and implement platform engineering. A lack of definition for DevOps enabled early adopters but didn't allow late-majority enterprises to be successful in their adoption of DevOps. The platform engineering community is in danger of repeating this mistake.
-
Software Testing through the Lens of Energy Management
I’m a software tester who observed that certain activities were getting me excited, while other simpler, shorter activities were draining and took a lot longer to get me motivated enough to even pick them up . This article is an experience report of how I discovered my personal energy system and superimposed it on a video game model, which also applies to the world of software testing.
-
Moving to .NET 7 MSMQ Alternatives
No MSMQ support is available in the new versions of .NET; if it’s time to move, this article presents a few considerations on what that transition can look like. It will explore some of the available options. By the end, you should see that even though it may be tough, there is a pathway forward.
-
Going from Architect to Architecting: the Evolution of a Key Role
This article explores the cultural change of moving towards shared architecture, and the role that the architect has evolved into; from one with an air of authority and singular vision, to one in which system design issues are surfaced, which require team-wide input to resolve. Teams being coached and guided towards shared ownership might be struggling with the paradigm shift of ownership.
-
The Future of Technology Depends on the Talent to Run it
Effective nearshore staff augmentation—a savvier form of outsourcing—allows organizations to bypass the skills gap and mitigate turnover. Nearshoring can help companies build great teams of professionals who are located in the same time zone, charge reasonable rates, and collaborate directly with in-house teams.
-
Colliding Communities, Cloud Native, and Telecommunications Standards
What happens when an ecosystem driven from the bottom up collides with a community characterized by top-down development? The 5g broadband cellular network standard by the 3rd Generation Partnership Project (3GPP), the Network Function Virtualization (NFV) standard by the European Telecommunications Standards Institute (ETSI), and the Service Function Chain RFC (request for comments) are examples.
-
Great Leaders Manage Complexity with Self-Awareness and Context Awareness
People's perception and expectations on leadership requires a leader to understand their own contextual significance which makes it difficult to become an appreciated leader. Also trivialisation many times unknowingly stands in the way of progress in complex situations. This article explores specific traits that distinguish people who repeatedly provide appreciated and appropriate leadership.
-
Adopting Low Code/No Code: Six Fitnesses to Look for
When selecting a no-code/low-code platform, six key fitnesses should be examined: purpose fit, cost fit, ops fit, user fit, use-case fit, and organization fit. The IT team should be heavily involved in this decision as they play a pivotal role in helping citizen developers with platform adoption.
-
What Does Technical Debt Tell You?
Technical debt is a popular metaphor for communicating the long-term implications of architectural decisions and trade-offs to stakeholders, but there are limitations to its usefulness. Incorporating quality attribute requirements, or using a different metaphor such as deferred maintenance, can help improve decision making.
-
Enabling Effective Remote Working - Principles and Patterns from Team Topologies
This article shares ideas, principles, and practices from Team Topologies (and related topics) to help organizations approach their structures' design and evolution to better support interactions in remote working. It also shares examples to showcase their impact when used to better approach organizational design, in general, and particularly to support remote working.
-
Using Serverless WebSockets to Enable Real-Time Messaging
This article reviews some of the most common live-user experiences with examples, discusses event-driven architectures to support real-time updates, and introduces common technology choices.
-
API Security: from Defense-in-Depth (DiD) to Zero Trust
Nearly all companies have experienced security incidents but few have an API security policy that includes dedicated API testing and protection. A defense-in-depth approach that includes boundary defense, observability, and authentication is recommended.