DevOps Archives - Page 44 of 91 - DEVOPS DONE RIGHT.

AWS Gateway LoadBalancer: A Load Balancer that we deserve

Nowadays, LoadBalancing is one of the basic needs for the application systems to perform optimally while considering some important factors like- scalability and high availability. Every cloud is providing LBaaS (LoadBalancing as a Service) as an offering so the consumers don’t have to worry about the setup and management of load-balancers by themselves.

But it’s not like that cloud is offering a single type of load balancer for every use case because for different use-case we require a different type of load balancer. For example- we have different load-balancers for Layer4 and Layer7 level traffic.

Recently AWS had a new family member in their load-balancer family and they named it “Gateway Load Balancer“. So gateway load-balancer is a load-balancing service provided by AWS to send traffic to the different appliances, applications, firewalls, etc. that are not part of the current VPC.

Learn everything about Amazon Cloudfront

Before going to Cloudfront functionality, we need to understand the CDN (Content delivery network) first, as Cloudfront is nothing but just a FAAS (functions as a service) platform provided by AWS, which we generally relate to the content delivery network(Cloudfront) in AWS cloud service provider.

CDN(Content Delivery Network)

A CDN is kind of a geographically distributed group of servers that are attached so that they can communicate with each other and provide fast delivery of any content such as HTML pages, images, videos, etc. The popularity of CDN services is continuously growing among organizations such as Netflix, Facebook, and Amazon as their major web traffic is served through CDN.

Now, let’s take a deep understanding of how CDN works in the AWS Cloudfront service.

We could think of a CDN as an ATM. Having a cash machine on practically every corner makes it fast, immediate access, and efficient to get money. There’s no wait time in long bank lines to get our money in hand.

In today’s time, a large portion of all internet content is delivered through CDNs. Here is a simple example:

Azure HA Kubernetes Monitoring using Prometheus and Thanos

Introduction

Long since Prometheus took on the role of monitoring the systems, it has been the undisputed open-source leader for monitoring and alerting in Kubernetes systems, it has become a go-to solution. While Prometheus does some general instructions for achieving high availability but it has limitations when it comes to data retention, historical data retrieval, and multi-tenancy. This is where Thanos comes into play. In this blog post, we will discuss how to integrate Thanos with Prometheus in Kubernetes environments and why one should choose a particular approach. So let’s get started.

Continue reading “Azure HA Kubernetes Monitoring using Prometheus and Thanos”

MongoDB Setup on Kubernetes using MongoDB Operator

MongoDB is a popular NoSQL database that supports large as well as small size of datasets. Just like any other database standalone setup, MongoDB is straightforward but we have to make a replicated or shared cluster of MongoDB, and there we have certain complications. Especially if we are doing these kinds of setups in orchestration tools like Kubernetes.

There is a lot of complexity in setting up MongoDB on Kubernetes that people(including me) have faced for a long time which I would like to highlight:-

Standalone setup is pretty straightforward but for replicated and sharded clusters additional mongo configurations are required.
In the replicated scenario, separate configurations need to be managed for the leader and follower.
Monitoring and access management of MongoDB inside Kubernetes is a little tricky part to handle.

Learn the Importance of Namespace, Quota & Limits

Let’s start with a scenario, whenever any application builds, we generally do have 3 environments on the basis of resources – dev for developers resources, test for testers resources, and prod for production resources. Likewise, we used to have a separate IT-Operational Team having strategies to maintain their environment resources. It was very time-consuming and many human resources were required.

We are in the microservices era where we follow the DevOps Methodology. The DevOps Team brings all the environment and strategies to maintain resources in one go. Resources are the ones who decide the behavior of your applications. We can apply the criteria to resources, so how can our application behave? To do this we can give the name to our resources, we can give the resources quota to the application, and can give resource ranges to the application.

Continue reading “Learn the Importance of Namespace, Quota & Limits”