Tutorial showing how to use Korifi to deploy applications to Kubernetes written in Ruby, Node.js, ASP.NET, and PHP on an Ubuntu server.

Network reliability is one of the most basic assumption mistakes made by microservices developers, let's see how to factor this unreliability when writing microservices.

In this article, learn how to launch an Apache Kafka with the Apache Kafka Raft (KRaft) consensus protocol and SSL encryption.

Let's continue our exploration of Python's magic methods in this second part of the series. This part will focus on numbers and containers, i.e., collections.

Brief overview of Apache Kafka and common use cases, current tools to scale multi-cluster deployments, and connectivity solutions to simplify multi-cluster deployments.

Learn what OpenTelemetry is and how it supports vendor neutrality for DevOps and SREs to monitor and observe microservices in the cloud.

Delve into the multifaceted complexities of a distributed Kubernetes ecosystem and cost implications; discuss the recommended FinOps practices for Kubernetes.

This article will explore a step-by-step guide on deploying the ELK Stack on Kubernetes. By the end of this guide, you'll have a fully functional ELK stack setup.

This article will serve as a comprehensive guide to Kubernetes security, aimed at helping developers protect their applications and data.

There are several Kubernetes tools that help you automate processes to ensure your deployments and workflows are optimized.

Discover how how Kubernetes can join forces with AI/ML to provide fine-grained control, security, and elasticity for AI/ML workloads.

Explore SPIFFE and SPIRE and learn how they secure and authenticate microservices in dynamic, multicloud, and multi-environment scenarios.

Find out what Gramma's been cooking in this latest comic from Daniel Stori, featured in the DZone 2023 Kubernetes in the Enterprise Trend Report.

Delve into the serverless trend advantages and highlight key open-source solutions that bridge the gap between serverless and Kubernetes.

The goal of this article is to present 3 popular extensibility architectural patterns from a developer's perspective using well-known programming principles.

Explore the world of containers and microservices in K8s-based systems and how they enable the building, deployment, and management of cloud-native applications at scale.

Look at the current state of managed Kubernetes offerings as well as options for self-managed clusters. Discuss the pros and cons as well as recommendations.

In this post, I write a little bit about the basic ideas of web server, Servlet container and its relation with JVM. I want to show that Servlet container is nothing more than a Java program. 1. What is a Web Server? To know what is a Servlet container, we need to know what is a Web Server first A web server uses HTTP protocol to transfer data. In a simple situation, a user type in a URL (e.g. www.programcreek.com/static.html) in browser (a client), and get a web page to read. So what the server does is sending a web page to the client. The transformation is in HTTP protocol which specifies the format of request and response message. 2. What is a Servlet Container? As we see here, the user/client can only request static webpage from the server. This is not good enough, if the user wants to read the web page based on his input. The basic idea of Servlet container is using Java to dynamically generate the web page on the server side. So servlet container is essentially a part of a web server that interacts with the servlets. Servlet container is the container for Servlets. 3. What is a Servlet? Servlet is an interface defined in javax.servlet package. It declares three essential methods for the life cycle of a servlet – init(), service(), and destroy(). They are implemented by every servlet(defined in SDK or self-defined) and are invoked at specific times by the server. The init() method is invoked during initialization stage of the servlet life cycle. It is passed an object implementing the javax.servlet.ServletConfig interface, which allows the servlet to access initialization parameters from the web application. The service() method is invoked upon each request after its initialization. Each request is serviced in its own separate thread. The web container calls the service() method of the servlet for every request. The service() method determines the kind of request being made and dispatches it to an appropriate method to handle the request. The destroy() method is invoked when the servlet object should be destroyed. It releases the resources being held. From the life cycle of a servlet object, we can see that servlet classes are loaded to container by class loader dynamically. Each request is in its own thread, and a servlet object can serve multiple threads at the same time(thread not safe). When it is no longer being used, it should be garbage collected by JVM. Like any Java program, the servlet runs within a JVM. To handle the complexity of HTTP requests, the servlet container comes in. The servlet container is responsible for servlets’ creation, execution and destruction. 4. How Servlet container and web server process a request? Web server receives HTTP request Web server forwards the request to servlet container The servlet is dynamically retrieved and loaded into the address space of the container, if it is not in the container. The container invokes the init() method of the servlet for initialization(invoked once when the servlet is loaded first time) The container invokes the service() method of the servlet to process the HTTP request, i.e., read data in the request and formulate a response. The servlet remains in the container’s address space and can process other HTTP requests. Web server return the dynamically generated results to the correct location The six steps are marked on the following diagram: 5. The role of JVM Using servlets allows the JVM to handle each request within a separate Java thread, and this is one of the key advantage of Servlet container. Each servlet is a Java class with special elements responding to HTTP requests. The main function of Servlet contain is to forward requests to correct servlet for processing, and return the dynamically generated results to the correct location after the JVM has processed them. In most cases servlet container runs in a single JVM, but there are solutions when container need multiple JVMs. From Program Creek

How to set up and use Karpenter for autoscaling and collecting underutilized spot and on-demand instances for AWS EKS.

How Kubernetes has lowered marginal costs of services, enabled composability, and driven an explosion of telemetry data needing improved observability.