InfoQ Homepage Design Content on InfoQ
-
Service Design: Consumer Journey Mapping
A process of identifying key customer interactions with the product. This is a holistic approach to envisioning customer interactions at various touchpoints through service design tools to help organizations to understand, visualize and envision their new or existing customer there by aligning their products.
-
What Does "Being Digital" Actually Mean?
Digital transformation is a key aim of many organisations these days, with varying levels of success. This is often due to a lack of understanding about what being digital really means. Being Digital is the re-imagining of business processes to be by default a fully online, fully automated process from end user interaction to back office processing, with no need for human intervention.
-
Harnessing the Power of Architectural Design Principles
Architecture principles epitomize architecture's function: to clearly define the necessary constraints on a system's design without prescriptively defining all the design details. A good set of principles can provide context and justification for design decisions and can foster team collaboration and communication.
-
Navigating the Ins and Outs of a Microservice Architecture (MSA)
A microservices architectures (MSA) is increasingly becoming an important way to deliver efficient functionality, but are just one aspect of a much larger picture. A good MSA implementation requires a solid understanding and design of both the inner architecture and the outer architecture of the system.
-
Refactoring to Reactive - Anatomy of a JDBC migration
Reactive programming offers built-in solutions for some of the most difficult challenges in programming, including concurrency management and flow control. So you might ask - how do I get there; can I introduce it in phases? In this article we transform a legacy application to a reactive model using RxJava.
-
Q&A with the Author on "Designing the Requirements”, an Alternative Approach
In the book “Designing the Requirements: Building Applications that the User Wants and Needs”, the author Chris Britton proposes an alternative path that goes from understanding the requirements to deliver spot on solutions.
-
Advanced Use Cases for the Repository Pattern in .NET
In our previous article, we looked at the basic patterns needed to implement a repository. In many cases these patterns were such a thin layer around the underlying data access technology they were essentially unnecessary. However, once you have a repository in place, many new opportunities become available.
-
Implementation Strategies for the Repository Pattern with Entity Framework, Dapper, and Chain
This article will focus on the basic functionality that one would find in a typical repository created with .NET. We’ll look at both general functionality and how that functionality would be implemented using three different styles of ORM: Entity Framework, Dapper, and Tortuga Chain.
-
Agile in the UK Government - An Insider Reveals All
The Government Digital Service (GDS) aims to transform the relationship between citizen and state, moving the UK towards becoming a world-leading digital-by-default government. Nick Tune explores what GDS has achieved with assessments, sharing agile practices and experiences, and open source software, and shares what isn’t working so well in government IT.
-
What’s Wrong With Using Design Templates?
By choosing a web design template, businesses save on time and the cost of developing their website. Templates are often hard to customize and generate a range of other issues that affect the website's performance an negatively impact the brand. Contrary to custom design, templates can only serve as a starting point for creating a web presence.
-
WTF requirements in Agile Product Development
The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.
-
Configure Once, Run Everywhere: Decoupling Configuration and Runtime
Configuration is one of the most widely used cross-cutting concerns in application development. Apache Tamaya is a new incubator project that brings standardized property management to Java.