InfoQ Homepage Architecture Content on InfoQ
-
Building Stronger Human Teams by Managing the Inner Lizards
Each of us has an inner lizard that frets constantly about our safety. People come with brains that are pre-configured to scan everything you say for threats to their safety. Learning to recognize when you're operating under reptilian influence is a great start. This article introduces some techniques to help you manage the lizard within you along with those around you.
-
Building Latency Sensitive User Facing Analytics via Apache Pinot
At QCon, a virtual conference for senior software engineers and architects covering the trends, Chinmay Soman talked about how you can use Apache Pinot as part of your data pipelines for building rich, external, or site-facing analytics.
-
Danske Bank’s 360° DevSecOps Evolution at a Glance
This article provides an overview of the ongoing DevSecOps evolution at Danske Bank, positioned within the broader transformation that the firm is performing. The main enablers and motivating factors of the evolution are outlined, with challenges discovered. The high level overview of the DevSecOps operating model, together with anti-patterns discovered and main lessons learned concludes it.
-
Implementing Microservicilites with Istio
Microservicilities is a list of cross-cutting concerns that a service must implement apart from the business logic. These concerns include invocation, elasticity and resiliency, among others. This article describes how a service mesh such as Istio may be used to implement these concerns.
-
Building Reliable Software Systems with Chaos Engineering
Advances in large-scale, distributed software systems are changing the game for software engineering. As an industry, we are quick to adopt practices that improve flexibility and improve feature velocity. If we can move quickly, can we do so without breaking things? Chaos Engineering practices can be used to navigate complexity and build more reliable systems.
-
Shifting to Continuous Documentation as a New Approach for Code Knowledge
Documentation is an important part of code development. However, documentation quickly becomes stale as code changes. Continuous documentation focuses on three principles: continuously verifying documents, documenting when it is most needed, and coupling the documentation to the code.
-
Microsoft's Low-Code Strategy Paints a Target on UIPath and the Other RPA Companies
Microsoft is investing big in the low code space and has put together a collection of products that is hard for other companies to match, capped recently by the announcement of PowerFX. The target in their sights is the Robotic Process Automation (RPA) companies such as UIPath, Automation Anywhere and Blue Prism who are closing big deals with big enterprises.
-
Evolutionary Architecture from an Organizational Perspective
Creating an architecture that can evolve over time is not simply a technical challenge, and requires collaboration with non-technical people in an organization to ensure the software adapts as needed.
-
Case Study: a Decade of Microservices at a Financial Firm
Microservices are the hot new architectural pattern, but the problem with “hot” and “new” is that it can take years for the real costs of an architectural pattern to be revealed. Fortunately, the pattern isn’t new, just the name is. So, we can learn from companies that have been doing this for a decade or more.
-
Keeping Technology Change Human
When we are at the forefront of so much change, it's easy to forget that other people around us find change more challenging. This article is a reminder to look beyond the code and processes, to consider how tech team actions can affect our users in emotional ways. It seeks to establish a few ways of thinking to help bring others along with us when working through technology change.
-
Containers Are Contagious and Often Misused
Let’s get something straight right right from the start— this article is not to argue that containers are bad; containers are certainly one of many great options developers have in their hands today. This article is also not scoped at the pros/cons of containers; my intent is just to present the developers and dev leads with some considerations around containers.
-
Local-First Cooperation: Autonomy at the Edge, Secured by Crypto, 100% Available
Why do two local devices need the cloud to be able to communicate? Shouldn't we be able to enable robust cooperation between nearby computing devices? This idea is the realm of local-first cooperation. In what follows, the author discusses the technologies used to make it function and a few places where work is still needed.