Barbara Liskovthe brilliant Turing Award winner whose career inspired so much modern thinking around distributed computingwas fond of calling out the power of abstraction and its role in finding the right interface for a system as well as finding an effective design for a system implementation.

Liskov has been proven right many times over, and we are now at a juncture where new abstractionsand eBPF, specificallyare driving the evolution of cloud native system design in powerful new ways. These new abstractions are unlocking the next wave of cloud native innovation and will set the course for the evolution of cloud native computing.

Before we dive into eBPF, lets first examine what cloud native is and why it needs to evolve.

Cloud native embraces a container model where a single kernel becomes the common denominator for managing many networking objects. We see related trends, like networks becoming namespace-based, where full-blown VMs are being replaced by containers or lightweight VMs. Cloud native shifts the scale and scope from a few VMs to many containers with higher per-node container density for efficient resource use and shorter container lifetimes. These dynamic IP pools for containers also have high IP churn.

The challenges dont end there.

Once you have stood up and bootstrapped your cluster there are Day 2 challenges like observability, security, multicluster and cloud management, and compliance. You dont just move to a cloud native environment with a flick of a switch. Its a progressive journey.

Once you have a cloud native environment set up, you will face integration requirements with external workloads (e.g., through more predictable IP addresses via service abstractions or egress gateways, like BGP for pod networking, CIDRs, services, and gateways). You will also have to deal with the successive migration toward IPv6-only clusters for better IAM flexibility, and NAT46/64 for interaction with legacy workloads and be able to connect multiple clusters on/off-prem in a scalable manner, with topology-aware routing and traffic encryption, and so much more.

These problems are only going to grow larger, with Gartner estimating that by 2025 over 95% of new digital workloads will be deployed on cloud native platforms, up from 30% in 2021.

The Linux kernel, as usual, is the foundation to solving these challenges, with applications using sockets as data sources and sinks and the network as a communication bus. Linux and Kubernetes have come together as the cloud OS.

But cloud native needs newer abstractions than currently available in the Linux kernel because many of these building blocks, like cgroups (CPU, memory handling), namespaces (net, mount, pid), SELinux, seccomp, netfiler, netlink, AppArmor, auditd, perf, were designed more than 10 years ago.

These tools dont always talk together, and some are inflexible, allowing only for global policies and not per-container policies. They dont have awareness of pods or any higher-level service abstractions, and many rely on iptables for networking.

As a platform team, if you want to provide developer tools for a cloud native environment, you can still be stuck in this box where cloud native environments cannot be expressed efficiently.

eBPF is a revolutionary technology that allows us to dynamically program the kernel in a safe, performant, and scalable way. It is used to safely and efficiently extend the cloud native capabilities of the kernel without requiring changes to kernel source code or loading kernel modules.

eBPF:

These capabilities allow us to safely abstract the Linux kernel and make it ready for the cloud native world.

Next lets dive into 10 ways the eBPF abstraction is helping evolve the cloud native stack, from speeding up innovation to improving performance.

Adding a new feature or functionality to the Linux kernel is a long process. In the typical patch lifecycle, you need to develop a patch, get it merged upstream, then wait until major distributions get released. Users typically stick to LTS kernels (for example, Ubuntu is typically on a two year cadence). So innovation with the traditional model requires kernel modules or building your own kernels, leaving most of the community out. And the feedback loop from developers to users is minimal to nonexistent. eBPF managed to break this long cycle by decoupling from kernel releases. For example, changes in Cilium can be upgraded on the fly with the kernel running and work on a large range of kernel releases. This allows us to add new cloud native functionality years before it would otherwise be possible.

New features can increase functionality, but also bring new risks and edge cases. Development and testing costs much more for kernel code versus eBPF code for the same functionality. The eBPF verifier ensures that the code wont crash the kernel. Portability for eBPF modules across kernel versions is achieved with CO-RE, kconfigs, and BPF type info. The eBPF flavor of the C language is also a safer choice for kernel programming. All of these make it safer to add new functionality to the kernel than patching directly or using a kernel module.

Traditional feedback loops required patching the in-house kernel, gradually rolling out the kernel to the fleet to deploy the change, starting to experiment, collecting data, and bringing the feedback into the development cycle. It was a very long and fragile cycle where nodes needed to restart and drain their traffic, making it impossible to move quickly especially in dynamic cloud native environments. eBPF decouples this feedback loop from the kernel and allows atomic program updates on the fly, dramatically shortening this feedback loop.

Instead of requiring rewrites of large parts of the user space stack, eBPF is able to piggyback on parts to the kernel and use them as-is while making integration dramatically easier. eBPF adds building blocks to the kernel that are too complex for other kernel subsystems, especially for new cloud native use cases. With eBPF, Cilium was able to easily add a NAT 46/64 gateway to connect IPv6-only Kubernetes clusters to IPv4-based infrastructure.

Recently, eBPF was used to fix a kernel bug in the veth (virtual Ethernet) driver that was affecting queue selection. (See the eBPF Summit talk, All Your Queues Are Belong to Us.) This on-the-fly fix enabled by eBPF avoided complex rollouts of new kernels, an especially time-consuming process for cloud providers. Cloud native workloads can bring new edge cases to the kernel, but on-the-fly fixes with eBPF make packet processing more resilient and reduce the attack surface from bad actors.

Traditional virtualized networking functions, such as load balancers and firewalls, are solved at a packet level. Every packet needs to be inspected, modified, or dropped, which is computationally expensive for the kernel. eBPF reframed the original problem by moving as close to the event source as possible, toward per-socket hooks, per-cgroup hooks, and XDP (eXpress Data Path), for example. This resulted in significant resource cost savings and allowed the migration from dedicated boxes to generic worker nodes. Seznam.cz was able to reduce their load balancer CPU consumption by 72x using eBPF.

By using eBPF for forwarding, we allow many parts of the networking stack to be bypassed, greatly improving networking efficiency and performance. For example, with eBPF, Cilium was able to implement a bandwidth manager that reduced p99 latency by 4.2x. It also helped enable BIG TCP and a new veth driver replacement that lets containers achieve host networking speeds.

eBPF reduces the kernels feature creep that slows down data processing by keeping the fast path to a minimum. Complex, custom cloud native use cases dont need to become part of the kernel. They simply become more building blocks in eBPF that can be leveraged in different edge cases. For example, by decoupling helpers and maps from entry points in eBPF, Cilium was able to create a faster and more customizable kube-proxy replacement in eBPF that can continue to scale when iptables falls short.

Given the churn in cloud native workloads, it can be difficult to find and debug issues. eBPF collectors make it possible to build low-overhead, fleet-wide tracing and observability platforms. Instead of having to modify application code or add sidecars, eBPF allows zero instrumentation observability. Troubleshooting production issues on-the-fly also can be done safely via bpftrace while allowing significantly richer visibility, programmability, and ease-of-use than old-style perf.

In cloud native environments, eBPF allows you to abstract away from high pod IP churn towards more long-lasting identities. IPs are meaningless given that everything is centered around pod labels and that the pod lifetime is generally very short with ephemeral workloads. By understanding the context of the process in the kernel, eBPF helps abstract from the IP to provide more concrete identity abstractions. With a secure identity abstraction for workloads, Cilium was able to build features like egress gateways for short-lived pods and mTLS.

Cloud native is shifting the requirements for platforms that need to support higher levels of performance and scalability along with constant change. Many of the Linux kernel building blocks that support these demanding workloads are decades old. Luckily, eBPF allows us to dynamically change the kernel to create abstractions that are ready for the cloud native world. eBPF is unlocking cloud native innovation, creating new kernel building blocks, and dramatically improving the performance of application platforms.

Bill Mulligan is a Cilium maintainer and heavily involved in the eBPF ecosystem. He works at Isovalent.

New Tech Forum provides a venue to explore and discuss emerging enterprise technology in unprecedented depth and breadth. The selection is subjective, based on our pick of the technologies we believe to be important and of greatest interest to InfoWorld readers. InfoWorld does not accept marketing collateral for publication and reserves the right to edit all contributed content. Send all inquiries tonewtechforum@infoworld.com.

Read more:
How eBPF unlocks cloud native innovation - InfoWorld

DUBAI, 20th March, 2023 (WAM) -- CodersHQ, one of the National Programme for Coders initiatives, in collaboration with Amazon Web Services (AWS), organised a breakfast with Chief Technology Officers (CTO), an interactive workshop that hosted Mark Schwartz, Enterprise Strategist at Amazon Web Services, titled Speed and Control and Centralisation & Decentralisation.

The workshop aimed to share experiences and strategies on the development of cloud computing, how to increase speed while maintaining flexibility, control, and agility, and its importance in enhancing productivity, that the private sectors CTOs have acquired.

Commenting on the workshop, Saqr Binghalib, Executive Director at the Minister of State for Artificial Intelligence, Digital Economy and Remote Work Applications Office, affirmed the importance of dialogues and workshops convening experts to share experiences aiming to develop the digital sector and ensure the sustainability of promising digital fields growth such as the Metaverse, Artificial Intelligence, Machine learning and Cloud Computing and their main role in enhancing digital utilisation, sharing success stories and being proactive in the future fields.

During the workshop, Mark Schwartz showcased the importance of cloud and digital deliverys techniques aiming to generate faster results with more control. He further explained the difference between the concepts of speed and control between the past and the present, pointing out that the benefits of digital tools to enabling different elements and enhancing speed and control in all sectors in a way to guaranteeing the best control as well as managing challenges and ensuring the success.

He said, In the past, organisations have assumed that speed and control were in opposition that going fast meant losing control. Today, with the tools of the digital age, the opposite is true. Government sectors and corporations can govern better, manage their challenges better, and make better use of their resources if they learn to move at speed."

Schwartz discussed the mechanisms of using the cloud and digital methods to obtain quick results with high control. He identified benefits of centralisation in improving efficiency, decreasing costs, increasing control as well as benefits of decentralisation in increasing speed and improving efficiency of response for customers, enhancing innovation, and managing challenges.

The session also discussed challenges of centralisation and decentralisation and the importance of exploring opportunities out of these challenges for development to make the best decisions and improve its efficiency.

The workshop came within the HQ meetups in CodersHQ aiming to gather like-minded people in different coding fields and supporting coders as one of the main pillars for achieving the UAE Digital Economy Strategy.

Read the original here:
Coders HQ organises breakfast with CTOs in collaboration with AWS -

Using the Cloud to Connect Farmers to Consumers Serves Opportunities to Both, With a Side of Efficiency  CropLife

Read more from the original source:
Using the Cloud to Connect Farmers to Consumers Serves Opportunities to Both, With a Side of Efficiency - CropLife

How AI, Coding, Blockchain, Cloud Computing will boost employability in the youth  India Today

See the original post:
How AI, Coding, Blockchain, Cloud Computing will boost employability in the youth - India Today