InfoQ Homepage Architecture & Design Content on InfoQ
-
/articles/type-systems-verifying-musical-correctness/en/smallimage/logo-1561528822846.jpg)
It Ain't Necessarily So: Exploring Type Systems for Verifying Musical Correctness
Chris Ford explores what makes music correct and how we might encode it in a type system.
-
/articles/notpetya-retrospective/en/smallimage/icon-1560945161288.jpg)
NotPetya Retrospective
As we hit the second anniversary of NotPetya, this retrospective is based on the author’s personal involvement in the post-incident activities. In the immediate aftermath, it seemed like NotPetya could be the incident that would change the whole IT industry, but it wasn’t—pretty much all the lessons learned have been ignored.
-
/articles/obscuring-complexity/en/smallimage/obscuring-complexity-s-1560786483000.jpeg)
Obscuring Complexity
One of the most important things that software architects do is manage the complexity of their systems in order to mitigate release disruption while maintaining sufficient feature velocity. When we cannot reduce complexity, we try to hide or shift it. Software architects tend to manage that complexity with the time-honored strategies covered in this article.
-
/articles/openapi/en/smallimage/open-api-s-1560967631428.jpeg)
Using OpenAPI to Build Smart APIs for Dumb Machines
This article discusses how to build, manage and maintain APIs with OpenAPI, including some of the most notable features in v. 3.0.
-
/articles/prometheus-monitor-applications-at-scale/en/smallimage/logo-1560849701397.jpg)
How to Use Open Source Prometheus to Monitor Applications at Scale
In this article, the author discusses how to collect metrics and achieve anomaly detection from streaming data using Prometheus, Apache Kafka and Apache Cassandra technologies.
-
/articles/cloud-transactions-dahan/en/smallimage/cloud-transactions-dahan-s-1559898649885.jpeg)
How Do We Think about Transactions in (Cloud) Messaging Systems? An Interview with Udi Dahan.
Do today's cloud-based messaging services have different transactional support than those that preceded it? If so, what are the implications? In this interview with distributed systems expert Udi Dahan, we explores the question.
-
/articles/correctness-versus-change/en/smallimage/Logo-1559817158528.jpg)
Correctness vs Change: Which Matters More?
In ongoing software development, our core work is changing code. Jessica Kerr argues that by building changeable software on top of existing, well-understood components, and by improving delivery automations, teams will get better at their core work of delivering value and "changing reality".
-
/articles/reduce-react-load-time/en/smallimage/reduce-react-load-time-s-1559640333321.jpg)
How We Reduced Our React App’s Load Time by 60%
React handles UI updates efficiently but it does not magically make your web app faster. As our application grew in size, we started noticing some drawbacks of our setup. Although we knew how React worked and how Redux manages state, our application had bloated in size. We started seeing application crashes and jank. It was time to drive down the technical debt and make performance improvements!
-
/articles/webassembly-blazor/en/smallimage/webassembly-blazor-s-1559028403198.jpeg)
WebAssembly and Blazor: A Decades Old Problem Solved
A framework, named Blazor because it runs in the browser and leverages a templating system or "view engine" called Razor, enables the scenario .NET developers almost gave up on. It doesn't just allow developers to build client-side code with C#, but also allows developers to run existing .NET Standard DLLs in the browser without a plugin. Here's the story of WebAssembly and Blazor.
-
/articles/service-mesh-api-federating/en/smallimage/service-mesh-api-federating-s-1558080393545.jpeg)
Towards a Unified, Standard API for Consolidating Service Meshes
Service mesh architectures enable a control and observability loop. At the moment, service mesh implementations vary in regard to API and technology, and this shows no signs of slowing down. Building on top of volatile APIs can be hazardous. Here we suggest to use a simplified, workflow-friendly API to shield organization platform code from specific service-mesh implementation details.
-
/articles/mitigate-pain-getting-giving-feedback/en/smallimage/mitigate-pain-getting-giving-feedback-s-1558074717961.jpeg)
How to Mitigate the Pain of Getting and Giving Feedback
Companies that encourage open and honest feedback do better than companies that do not. Nonetheless, giving feedback is difficult because social and physical pain share some of the same neural circuitry. Hence, feedback can feel physically painful, as Sarah Hagan discusses in her 2018 QCon San Francisco talk . Hagan uses scientific research to demonstrate how to give feedback properly.
-
/articles/application-integration-service-mesh/en/smallimage/role-application-integration-cloud-native-microservices-landscape-logo-small-1557478517420.jpg)
Application Integration for Microservices Architectures: A Service Mesh Is Not an ESB
A service mesh is only meant to be used as infrastructure for communication between services, and developers should not be building any business logic inside the service mesh. Other frameworks and libraries can be used to implement cloud native enterprise application integration patterns.