InfoQ Homepage Architecture 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.
-
Q&A with Immuta on the Implications of EU’s General Data Protection Regulation (GDPR)
InfoQ talked with Immuta’s Andrew Burt and Steve Touw, to better understand the implications and challenges of the EU's Global Data Protection Regulation, which will come into effect in May 2018.
-
Virtual Panel: Microservices in Practice
Microservices have gone from development practices for the select few to something many developers in a range of organisations are embracing. Some believe that technologies that can assist with developing and adopting microservices are ineffective without associated changes within the organisations. We spoke with panelists to get different perspectives on the state of the art with microservices.
-
The Misaligned Middle and Getting off the Hamster Wheel Using Kanban
At the Agile 2016 conference, Dominica DeGrandis and Julia Wester of Leankit gave talks on helping middle managers adapt to change and how Kanban can be used to identify problems in workflows, which people need to address.
-
Might the Blockchain Outlive Bitcoin?
Crypto-currency remains controversial, and Bitcoin, a leading open source initiative to create an alternative form of currency, is at the center of this controversy. Here, the author provides an update on the state of Bitcoin in particular, and examines the future of crypto-currency in general.
-
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.
-
Developing Transactional Microservices Using Aggregates, Event Sourcing and CQRS - Part 2
This article concludes the description of a way to develop microservices using Domain Driven Design, Event Sourcing and Command Query Responsibility Segregation (CQRS). The practical considerations and benefits of this approach are compared with other options.
-
Chaos Engineering
Modern software-based services are implemented as distributed systems with complex behavior and failure modes. Many large tech organizations are using experimentation to verify such systems' reliability. Netflix engineers call this approach chaos engineering. They've determined several principles underlying it and have used it to run experiments. This article is part of a theme issue on DevOps.
-
How Difficult Can It Be to Integrate Software Development Tools? The Hard Truth
Integrating tools used in software development and delivery is very hard. Getting endpoints to inter-operate is not a purely technical challenge, it’s more of a business problem. While there are a few choices in selecting the technical integration infrastructure (integration via APIs or at the database layer), the real challenges have more to do with friction caused by the dissimilarities.
-
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.
-
How Zalando Delivers APIs with Radical Agility
InfoQ interviewed Thomas Fraustein, architect at Zalando, about his team’s radical agility development organization that is optimized for an API-first approach. He explains what an API-first approach is, and provides tips on building good APIs for scalable microservice architectures where a large number of services are offered efficiently.