InfoQ Homepage Design Content on InfoQ
-
/articles/contract-driven-development/en/smallimage/microservices-done-right-using-contract-driven-development-small-1671646587378.jpg)
Microservices Integration Done Right Using Contract-Driven Development
Build your microservices and micro-frontend in parallel and deploy them independently without worrying about integration issues, by leveraging API specifications such as OpenAPI and AsyncAPI as executable contracts to shift left the identification of compatibility bugs with Contract Driven Development using Specmatic, thereby removing the need for integration testing.
-
/articles/craftleadership-developers-craft-code/en/smallimage/small-1669118526409.jpg)
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.
-
/articles/designops-improve-process/en/smallimage/logo-1658847451817.jpg)
Why DesignOps Matters: How to Improve Your Design Processes
DesignOps is a combination of practices and a mindset that improves design workflow, facilitates designer-developer handoffs, enhances the way products and services are crafted, and enables projects to evolve at a faster pace. Design processes may be more complex, dispersed and chaotic than they should be. There are ways to adapt to digital transformation and establish well-functioning DesignOps
-
/articles/spark-ux-revolution/en/smallimage/logo-1658734521586.jpg)
How to Spark a Consumer-Grade UX Revolution
Turning end-users into advocates is one of the most powerful things SaaS companies can accomplish today. This can be a major project for a company, but it’s a revolution that can start small - and start today. Here we cover how to kick-off, manage, implement and iterate upon adding consumer-grade UX to the services that you own.
-
/articles/design-first-api-development/en/smallimage/design-first-approach-API-development-small-image-1650616561277.jpg)
Design-First Approach to API Development: How to Implement and Why It Works
With the rapid growth of the API industry, developers and technology leaders alike need to know how to create a successful and scalable API program that will drive business value. Developers should consider prioritizing a design-first approach to building APIs which will ensure a positive experience for all stakeholders.
-
/articles/architecture-trends-2022/en/smallimage/InfoQ-Trend-Report-logo-small-1648721970880.jpeg)
Software Architecture and Design InfoQ Trends Report—April 2022
An overview of how the InfoQ editorial team sees the Software Architecture and Design topic evolving in 2022, with a focus on what architects are designing for today.
-
/articles/agile-values-tech-people-lead/en/smallimage/logo-1644331481832.jpg)
Embracing Agile Values as a Tech and People Lead
Having worked as a software developer, the agile community has been a great source of inspiration to me to find better ways of working. In my first leadership role, I incorporated the agile mindset which helped me to get everyone working towards a joint goal: refactoring an inherited codebase for scalability, while enabling cross functional teams to work as autonomously as possible.
-
/articles/data-application-process/en/smallimage/logo-1638797109490.jpg)
You’re Doing it Wrong: it’s Not about Data and Applications – It’s about Processes
Classic developer thinking tends to approach application design from a data-centric point of view. When the domain is process management, that often leads to excess complexity and work; it also (wrongly) over-reduces proactive processes to quick bursts of automation triggered by data changes. There’s a better way to do this: start with the process.
-
/articles/design-patterns-for-serverless-systems/en/smallimage/logo-1638174359294.jpg)
Design Patterns for Serverless Systems
After shortly introducing design patterns at different levels of abstractions, this article will present a few patterns specifically suited to serverless systems, including the Pipes and Filters pattern and show a POC implementation using AWS EventBridge.
-
/articles/microservices-concepts-patterns/en/smallimage/Microservices-the-letter-and-the-spirit-small-image-1637327649178.jpg)
Microservices — the Letter and the Spirit
Microservices to be a pattern of ‘decoupled services’ managed to get the best out of it (the underlying understanding of the pattern (‘small’ vs ‘decoupled’) forces developers to take certain design decisions that are consistent with these objectives. In this article discuss we will discuss well and poor implementations: ‘small-services’ vs ‘decoupled-services’ or ‘Letter’ vs the ‘Spirit’.
-
/articles/microservices-inside-out/en/smallimage/turning-microservices-inside-out-small-image-1627634447180.jpg)
Turning Microservices Inside-Out
Turning microservices inside-out means moving past a single, request/response API to designing microservices with an inbound API for queries and commands, an outbound APIs to emit events, and a meta API to describe them both. A database can be supplemented with Apache Kafka via a connecting tissue such as Debezium.
-
/articles/technology-change-human/en/smallimage/logo-1621267095641.jpg)
Keeping Technology Change Human
When we are at the forefront of so much change, it's easy to forget that other people around us find change more challenging. This article is a reminder to look beyond the code and processes, to consider how tech team actions can affect our users in emotional ways. It seeks to establish a few ways of thinking to help bring others along with us when working through technology change.