ABOUT THE AUTHOR

Paweł Parol

Engineering Manager, Solutions Architect

Paweł Parol is a solutions architect and engineering manager with many years of experience in the IT/telco industry. Throughout his career, he has worked on both operational and research projects. His main areas of interest include cloud-native solutions, Kubernetes and AI/ML. Paweł is the author of several scientific publications, e-books, blog posts and technical videos and a speaker at conferences, webinars and workshops.

Paweł Parol

CONNECT WITH PAWEŁ PAROL

Linkedin

Recent posts by Paweł:

Thumbnail of an article about 5 examples of what you can do with Kubernetes Gateway API
NETWORKS

5 examples of what you can do with Kubernetes Gateway API

In this article, we’ll cover five practical examples of what you can do with the Kubernetes Gateway API, showing you how it goes beyond Ingress’ capabilities.
Multiple authors

Multiple authors

Thumbnail of an article about Network Automation Forum AutoCon3 2025: insights and summary
NETWORKS

Network Automation Forum AutoCon3 2025: insights and summary

Many of the talks at AutoCon3 touched on fundamental issues related to network automation, including what to pay attention to in order to meet your goals and achieve real improvements instead of getting lost.
Paweł Parol

Paweł Parol

Thumbnail of an article about Beyond container orchestration: 5 surprising Kubernetes use cases you need to know
CLOUD

Beyond container orchestration: 5 surprising Kubernetes use cases you need to know

Kubernetes is a popular and powerful platform for running containers. Whether you plan to deploy your applications or other workloads on-prem, in the cloud, or in a hybrid manner, in all cases, they can be containerized and adapted to run in a Kubernetes cluster.
Paweł Parol

Paweł Parol

Thumbnail of an article about [interview] Unlocking the future: A glimpse into the world of R&D at CodiLime
DATA
NETWORKS

[interview] Unlocking the future: A glimpse into the world of R&D at CodiLime

In the ever-evolving landscape of technology, research and development (R&D) plays a pivotal role in driving innovation, pushing the boundaries of knowledge, and shaping the future of industries. R&D is the heart of organizations that innovate, explore, and create, and it is the engine behind breakthroughs that change the way we live and work. In this interview, we’ll delve into the world of R&D with Paweł Parol, the leader of one of the R&D teams at CodiLime. Paweł Parol: Well, in short, R&D stands for research and development.
Multiple authors

Multiple authors

Thumbnail of an article about Introduction to network telemetry
OBSERVABILITY
NETWORKS

Introduction to network telemetry

You may have already heard about network telemetry, but you are not sure you understand well enough what exactly is behind it. If that's the case, you'll find the right explanation in this article. The term "network telemetry" can be understood in different ways. Over the years, it was not completely clear for everyone. Following the RFC 9232, you will come across the following understanding of the terms "network telemetry" and "telemetry data"- “Network telemetry is a technology for gaining network insight and facilitating efficient and automated network management.
Paweł Parol

Paweł Parol

Thumbnail of an article about In-band network telemetry — what is it all about?
OBSERVABILITY
NETWORKS

In-band network telemetry — what is it all about?

In-band network telemetry is one concept from a wide range of available solutions for network telemetry. If you want to know what this approach is all about and how it has been adopted so far, please read on. Over the years, a wide variety of protocols, methods, and tools have been developed for network telemetry. These solutions are quite diverse and are used depending on the specific context and needs. Some time ago, one more concept appeared on the map: in-band network telemetry. The approach here is to gather so-called telemetry metadata for packets traversing network segments.
Multiple authors

Multiple authors

Thumbnail of an article about From Kubernetes Ingress to Kubernetes Gateway API
CLOUD
NETWORKS

From Kubernetes Ingress to Kubernetes Gateway API

If you've ever touched on application networking in Kubernetes, it's more than likely you've come across Ingress. However, it is worth knowing that Ingress has a worthy successor in the form of Kubernetes’ Gateway API. If you want to get familiar with this new API, this article is what you need. Ingress is a Kubernetes API object that has been widely used for many years. It allows you to handle traffic entering the Kubernetes cluster from outside and to route it to multiple Services running in the cluster.
Paweł Parol

Paweł Parol

Thumbnail of an article about Service mesh vs. Kubernetes Ingress — what is the difference?
NETWORKS
CLOUD

Service mesh vs. Kubernetes Ingress — what is the difference?

Service mesh and Ingress are two solutions used in the area of ​​application networking in Kubernetes. In this article you will see what characterizes each of them and understand where the real difference between them is. A service mesh is a kind of special “system” for communication between applications, different components of an application based on microservices architecture, or between various other workloads running in virtual environments, such as Kubernetes. The solution provides a rich set of features in the fields of traffic management, reliability, resilience, security, and observability.
Paweł Parol

Paweł Parol

Thumbnail of an article about What is a service mesh — everything you need to know
NETWORKS
CLOUD

What is a service mesh — everything you need to know

A service mesh is an increasingly popular solution in the area of ​​application networking, in Kubernetes and other environments. If you are still not familiar with the concept, in this article you will find everything you need to know before taking a deeper dive. Over the past few years, we have seen a shift away from approaches based on monolithic code when designing software applications. Instead, modern design is based on microservices architecture. At the end of the day, it is about delivering basically the same business logic, not in the form of a large monolith but as a collection of loosely coupled and independently deployable services.
Paweł Parol

Paweł Parol

Thumbnail of an article about Is Network Service Mesh a service mesh?
NETWORKS
CLOUD

Is Network Service Mesh a service mesh?

Service mesh solutions are increasingly becoming an important element of modern applications built on the basis of microservices architecture. But here and there, you can also hear about a project called Network Service Mesh. Is it another variation on the service mesh theme or something completely different? A service mesh is a kind of “network” that connects all microservices within a given application. In fact, it is extra software that acts as an intermediary layer between services and provides a wide range of functions in the fields of security, observability, and traffic management, as well as reliability and resilience.
Multiple authors

Multiple authors

Thumbnail of an article about How to build CNFs using Ligato framework
NETWORKS
CLOUD

How to build CNFs using Ligato framework

Cloud native network functions (CNFs) are a hot topic today. In this blog post, I will take a stab at explaining why and also present the Ligato framework, which allows you to build your custom CNFs. We started talking about Virtual Network Functions (VNFs) a few years ago when the concept of Network Function Virtualization (NFV) appeared. In short, it is that network functions can be deployed as virtual machines (VMs) instead of being delivered on dedicated hardware offered by vendors. Over time, telco operators and service providers launched their first field trials and then roll-outs of network functions based on this paradigm.
Paweł Parol

Paweł Parol

Thumbnail of an article about Why Vector Packet Processing is worth your time
NETWORKS

Why Vector Packet Processing is worth your time

The Vector Packet Processor (VPP) is a high-performance packet-processing stack that can run on commodity CPUs. In this article, I will take a closer look at what distinguishes this technology from others and how helpful it can be in meeting the demand for efficient network solutions. Regardless of the specific hardware or software implementation at the dataplane level, packet processing can be generally described as a sequence of operations that are performed on packets. This can be represented as a graph in which each vertex corresponds to an operation.
Paweł Parol

Paweł Parol

Thumbnail of an article about P4-programmable smartNIC controlled by ONOS (video)
SOFTWARE DEVELOPMENT
NETWORKS

P4-programmable smartNIC controlled by ONOS (video)

The traditional NIC (Network Interface Card) is a relatively simple device equipped with Ethernet interface(s) and used to enable connectivity between machines. SmartNICs, by contrast, offer much more sophisticated capabilities and allow you to perform advanced operations on packets. SmartNICs are thus perfectly suited to optimize network performance in a data center, especially those that are programmable and offer the computing resources required.
Multiple authors

Multiple authors

Thumbnail of an article about SmartNICs with P4 support
SOFTWARE DEVELOPMENT
NETWORKS

SmartNICs with P4 support

In the first part of this blogpost we discuss the idea of using smartNIC solutions to optimize network performance in a data center. In the second part, we review the currently available (July 2020) smartNIC solutions that can be programmed with P4. A paradigm of edge-computing has been gaining in popularity of late. The term itself can refer to many sub-technologies and have many meanings. One of them is the existence, next to the centralized, large data center, of those small or very small, located closer to the end-user.
Paweł Parol

Paweł Parol

Thumbnail of an article about P4 Network Programming Language — what is it all about?
SOFTWARE DEVELOPMENT
NETWORKS

P4 Network Programming Language — what is it all about?

The programming language P4 is gaining in popularity in the network industry and is considered the next step in the SDN evolution. In this blog post, I will take a closer look at P4 and try to show why it is so important. Network devices like switches or routers are most commonly designed ”bottom-up.” The switch vendors that offer products to their clients usually rely on external chips from 3rd party silicon vendors. The chip is the heart of the system and in practice determines how device OS is realized and what functionality it can offer.
Paweł Parol

Paweł Parol

Get your project estimate

For businesses that need support in their software or network engineering projects, please fill in the form and we'll get back to you within one business day.

We guarantee 100% privacy.