InfoQ Homepage Networking Content on InfoQ
-
Optimizing Wellhub Autocomplete Service Latency: a Multi-Region Architecture
Every company wants fast, reliable, and low-latency services. Achieving these goals requires significant investment and effort. In this article, I will share how Wellhub invested in a multi-region architecture to achieve a low-latency autocomplete service.
-
How to Minimize Latency and Cost in Distributed Systems
Explore the benefits and challenges of microservices architecture in cloud environments, focusing on achieving resilience and high availability while managing costs and performance issues.
-
Service Assurance in Private LTE/5G Networks
This article talks about service assurance in the context of cellular networks, how private networks pose additional needs, and how an end-to-end service assurance framework can be designed and developed for such networks.
-
Writing Cloud Native Network Functions (CNFs): One Concern per Container
This article discusses the “one concern, one process” design for containers and Cloud native network functions (CNFs).
-
The Future of Service Mesh is Networking
On this journey, we will discover that, to quote David Mooter, “The future of service mesh is as a networking feature, not a product category, as far out of sight and mind from developers as possible—and that is a good thing.”
-
What Does Zero Trust Mean for Kubernetes?
Zero trust is a powerful security model that’s at the forefront of modern security practices. It’s also a term that is prone to buzz and hype, making it hard to cut through the noise. So what is zero trust, exactly, and for Kubernetes, what does it mean in concrete terms? In this article, we’ll explore what zero trust is from an engineering perspective.
-
Cloud Native Network Functions Are Here
Compute elasticity, for instance, is reasonably allocated with virtual machines, containers, and orchestrators and managed with CI/CD pipelines. Network elasticity seems to be lacking in implementation. In this article, we show that cloud native network functions are an attempt to bring network applications into the cloud native world.
-
The What and Why of Programmable Proxies
A question which gets often asked is “What is a programmable proxy, and why do I need one?” This article tries to answer this question from different perspectives. We will start with a brief definition of what a proxy is, then discuss how proxies evolved, explaining what needs they responded to and what benefits they offered at each stage. Finally, we discuss several aspects of programmability.
-
A Recipe to Migrate and Scale Monoliths in the Cloud
In this article, I want to present a simple cloud architecture that can allow an organization to take monolithic applications to the cloud incrementally without a dramatic change in the architecture. We will discuss the minimal requirements and basic components to take advantage of the scalability of the cloud.
-
How to Bridge the Gap between Netops and Secops for Ultimate Network Management and Security
Sometimes it can seem like a new IT management paradigm arrives every week. First, we had DevOps; then DevSecOps; now the most innovative organizations are talking about AIOps and even NetAIOps. Yet what is often forgotten about in this rush to name new ways of working is that many of them have been in place in the best-run teams for decades - a great example of this is NetOps and SecOps.
-
The Kollected Kode Vicious Review and Author Q&A
Addison Wesley Professional The Kollected Kode Vicious by George V. Neville-Neil aims to provide thoughtful and pragmatic insight into programming to both experienced and younger software professionals on a variety of different topics related to programming. InfoQ has taken the chance to speak with author Neville-Neil about his book.
-
Donkey: a Highly-Performant HTTP Stack for Clojure
Donkey is the product of the quest for a highly performant Clojure HTTP stack aimed to scale at the rapid pace of growth we have been experiencing at AppsFlyer, and save us computing costs. In this article, we’ll briefly outline the use-case for a library like Donkey and present our benchmarks. Finally, we will discuss Clojure and immutability, and some of our design decisions.