Facilitating the spread of knowledge and innovation in professional software development



Choose your language

InfoQ Homepage Development Content on InfoQ

  • 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 as well as on Jonathan Locke’s blog State of the Art.

  • 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’.

  • 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.

  • 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.

  • 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.

  • 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.

  • Overriding Sealed Methods in C#

    In this article, the author demonstrates how we can change the behavior of sealed methods in C#. This can be done by understanding Operating System mechanisms and how the .NET platform generates and compiles code. The author illustrates these techniques using real-world scenarios, including the modification of the WinPAI wrapper.

  • The Renaissance of Code Documentation: Introducing Code Walkthrough

    The Continuous Documentation methodology is a useful paradigm that helps ensure that high-quality documentation is created, maintained, and readily available. Code Walkthroughs take the reader on a “walk” — visiting at least two stations in the code — describe flows and interactions, and often incorporate code snippets.

  • Five Things to Remember When Upgrading Your Legacy Solution

    Legacy software is still employed, even though it frequently fails to meet critical demands and core business operations. By choosing the right modernization strategy and software development teams, you can easily cut down on high legacy software maintenance costs and increase productivity.

  • Are Canary Releases an Alternative to Testers?

    Canary releases enable product owners to check how a new feature is getting adopted by users by rolling it out to a small percentage of users and then incrementally rolling it out to a wider audience. Product owners might feel tempted to discontinue or reduce testing upon adopting canary releases, but decisions should be approached cautiously as they can have serious and unintended consequences.

  • How to Harden Applications against IIoT Security Threats

    This article will explore two sides of the IIoT security equation: understanding how and why IIoT systems can become vulnerable to hacking attempts, and which solutions and strategies are available to harden them. It will provide also a set of best practices to address IoT security concerns.

  • Applying Software Delivery Metrics and Analytics to Recover a Problem Project

    Problem software delivery projects can be recovered mid-flight if Value Stream Management (VSM) analytics are used in a forensic way to uncover the root-cause of the issues. The root-cause metrics areas considered include: People Availability; Team Stress; Backlog Health; Sprint Accuracy; Process Efficiency; Story Management; and Defect Gen. A root-cause RAG reports shows key mitigations.