InfoQ Homepage Architecture Content on InfoQ
-
/articles/java-jvm-trends-2021/en/smallimage/InfoQ-Trend-Report-logo-1641794256028.jpeg)
Java InfoQ Trends Report—December 2021
This article provides a summary of how the InfoQ Java editorial team and various Java Champions currently see the adoption of technology and emerging trends within the Java and JVM space in 2021.
-
/articles/avoiding-technical-bankruptcy/en/smallimage/avoiding-technical-bankruptcy-small-image-1640173923994.jpg)
Avoiding Technical Bankruptcy: a Whole-Organization Perspective on Technical Debt
Technical debt is not primarily caused by clumsy programming, and hence we cannot hope to fix it by more skilled programming alone. Rather, technical debt is a third-order effect of poor communication. What we observe and label “technical debt” is the by-product of a dysfunctional process. To fix the problem of accumulating technical debt, we need to fix this broken process.
-
/articles/getting-started-grpc-dotnet/en/smallimage/logo-1638894843213.jpg)
Getting Started with gRPC and .NET
In this article, the author introduces the core concepts behind gRPC and how it can be used with API development. The basic pros and cons of using gRPC instead of REST are also explained with a scenario analysis. The text is illustrated with a step-by-step tutorial on how to use gRPC to develop streaming services in .NET.
-
/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/java-external-rules-engine/en/smallimage/logo-1637682106961.jpg)
Lightweight External Business Rules
Complex enterprise applications usually come with varying business logic. Such conditions and subsequent system actions, known as rules, are ever varying and demand involvement of domain specific knowledge more than technology and programming. The rules must reside outside the codebase, authored by people with core domain expertise with minimal tech knowledge.
-
/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/introducing-kivakit/en/smallimage/logo-1637780334611.jpg)
Introducing the KivaKit Framework
In this article, we take a brief tour of the KivaKit open source Java microservices application framework. KivaKit is a collection of mini-frameworks designed to work together. Each mini-framework is described in more detail at https://www.kivakit.org as well as on Jonathan Locke’s blog State of the Art.
-
/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/financial-software-low-code/en/smallimage/logo-1637135531983.jpg)
Faster Financial Software Development Using Low Code: Focusing on the Four Key Metrics
Low code/no code can help firms achieve the four key performance metrics described in the State of DevOps Reports and Accelerate, to achieve a faster pace of software development. Financial services especially stand to benefit from the trend of adopting low code/no code to drive digital transformation.
-
/articles/testing-blockchain-solutions/en/smallimage/logo-1637008540204.jpg)
Solutions for Testing Blockchain: Private Blockchains, Permutations, and Shifting Left
Blockchain is an emerging software architecture that has the potential to be a big disruptor in the industry. With change however, comes the added risk of quality issues. As developers and test engineers, we need to be prepared for those changes to better adapt to the new technology and allow for the continued development of software and products through it, without compromising on quality.
-
/articles/api-mocking-break-dependencies/en/smallimage/using-API-first-development-API-mocking-to-break-critical-path-dependencies-small-1636989383108.jpg)
Using API-First Development and API Mocking to Break Critical Path Dependencies
Teams are using API mocking to break critical path dependencies and enable what were serial execution sequences into parallel paths. This article looks at where mocks should be used for the greatest impact and provides a model to estimate the effect of implementing API mocking and an API-first approach.
-
/articles/cloud-infra-complexity/en/smallimage/logo-1636716177680.jpg)
Reducing Cloud Infrastructure Complexity
Cloud computing adoption has taken the world by storm, and is accelerating unabated. According to Flexera’s annual State of the Cloud Report for 2020, 93% of respondents used multi or hybrid cloud strategies. This article examines different aspects of cloud infrastructure complexity, and approaches to mitigate it.