InfoQ Homepage Architecture Content on InfoQ
-
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.
-
Java Champion Josh Long on Spring Framework 6 and Spring Boot 3
Microservices show where Java lags behind other languages. Reactive programming provides a concise DSL to express the movement of state and to write concurrent, multithreaded code with better scaling. Developing in Spring Boot works well even without special tooling support. Josh Long is excited about Project Loom, Java optimization in Project Leyden, and Foreign-Function access in Project Panama.
-
Craftleadership: Craft Your Leadership as Developers Craft Code
Learning software craftership made me reconsider how I wrote code. Being an experienced software team manager, I try to reevaluate my management practices in the same way: what could test-driven management or pair-management be? Here I propose different insights on how software craftership tools and mindset are transposable to the management domain.
-
Are Your “Value Streams” Keeping You Stuck in the Past?
The essence of business agility is being able to respond quickly and systematically to feedback. As a means of achieving business agility, value stream management falls short, and ends up being not very different from what organizations have done for a long time: using program management practices to coordinate work across different teams in a large organization.
-
The Future of DevOps is No-Code
The need for high-quality DevOps personnel is skyrocketing, but it is harder than ever to find enough staff. It is possible to augment your DevOps organization using no-code and low-code tooling. Low-code and no-code tools can free up existing developers by reducing the time spent on integrating and administering DevOps toolsets.
-
Build, Test, and Deploy Scalable REST APIs in Go
In this article, we'll look at how to use the gin framework to create a simple Go application. We will also learn how to use CircleCI, a continuous deployment tool, to automate testing and deployment.
-
Are They Really Using It? Monitoring Digital Experience to Determine Feature Effectiveness
This article reflects on the challenges of determining user experience and effectiveness and how modern techniques such as Real User Monitoring and Application Performance Monitoring can determine the true effectiveness of features. It includes stories from banking to show which measures can help agile teams determine not only if features are being used, but diagnose other common issues too.
-
Using Remote Agile Governance to Create the Culture Organisations Need
Governance and culture are inextricably intertwined, and creating an environment where people thrive is the most important governance responsibility. Sadly, in many organisations governance is perceived as slowing things down and impeding progress, yet effective governance is an enabler that removes blockages and enables flow.