Archives

Imagine a situation where you have a script or executable file that always needs to be ran by a particular user, simply because that user has proper access rights for the actions taken by the script. Also you are willing other users to be able to execute that script, but ultimately that needs to be ran as the original user of the script(as that user only has the required permission sets for the actions taken).

By default Linux applications and programs runs with the same exact permissions of the user who executes it. Due to this reason, we need a good solution for the above mentioned situation (ie: All users should be able to execute a program owned by a particular user as if the owner himself executed it).

Microservices based architecture has got a lot of media traction during the last few years. Plenty of blogs and articles have already been written about the benefits of microservices based architecture. Its nothing but a unique way of designing applications as different small components, which can be independently deployed as individual services.
 

In short, microservice architecture is nothing but an approach to application development, where an application is dissected to different components, and each application components are developed individually,packaged individually, and deployed individually, in individual processes.
 

In our previous tutorials, we talked about introduction to docker containers, docker installation, running our first container, pulling images, creating images etc. But we haven't talked about how docker does networking. Its really important to understand the networking part of docker, as the primary use case of Docker is to create services that users or other services will connect and communicate to.

The general Idea of DNS is to provide an IP address in return for a requested name. The normal regular and common configuration is to respond with the same answer no matter from where the request originated.

However, there are requirements and use cases, where you need to configure your DNS server with different set of addresses for the same domain name. Lets take an example to understand this. Let's say you have a DNS server and wants to use the same dns server for requests from internet as well as for requests from the private network. It does not make sense to respond back with the same answer for both the types. Because your internal private network users should access your services through the private LAN ip addresses itslef(which will be much better in terms of performance as well as latency) rather than accessing through the Public facing internet address.

With the increasing growth of internet users, the volume of traffic that web based companies deal with has increased dramatically. There are different solutions to cope up with this increasing traffic. One solution is to scale your servers vertically(ie: Simply add more CPU and Memory Resources to your server.), which of course cannot be done after a certain extent.

Another solution is to scale the server horizontally(ie: Add more servers that can deal with the surge in traffic.). This mechanism is generally known as clusters. In a cluster, multiple servers act together as a single component providing the required services to end users.

When traffic/load increases, we can simply add more servers to the cluster, therefore it is more scalable.

Extended Filesystem being the default file system in Linux, we will be focusing ext file system in this article to understand superblocks.

Before we get to understanding Superblocks in a file system, let’s understand some common terminologies and building blocks of a file system.

As I mentioned in my earlier tutorials, Docker images are the source code for our containers. Images are the main building block of a container. In this tutorial we will learn about building our own Docker Images.

Before going ahead with this tutorial, if you are new to Docker, I recommend reading all of the below posts.

Read: Hypervisor vs Containers

Read: How to Install Docker

Before going ahead with this tutorial, I would recommend to read the below two tutorials to understand containers and Docker installation process. This article assumes that you have docker installed on your system and is waiting to accept commands.

Read: Difference between Hypervisor and Container Virtualization

Read: How To Install Docker

If you are a linux user or a linux system admin or you are working in a production environment then you have to know about the software disk management and all the methods to provide flexblibity in storage management.In storage management you must have indepth knowledge of lvm.But before lvm you must have sound knowledge of volume group.

This is a detail tutorial on linux volume group.Everything we mentioned here in this article will be directly or indirectly related with Linux Volume Group.We will learn how to manage Storage Device concerned with volume group using command line.vgcreate vgremove vgchange vgconvert vgreduce vgextend vgmerge vgsplit and vgrename  are those linux command on which we are going to discuss in detail inside this tutorial.

First we need to create Physical Volumes that will be used to create Volume Group.

GNU/Linux, inspired from UNIX, has become the most widely adopted server operating systems out there. Adopters of Linux includes tech giants like Google, Facebook, Twitter, Yahoo, Amazon, and the list goes on and on.. The adoption rate of Linux in Desktop market cannot be calculated accurately, because, unlike proprietary software, the sources from where people get their copies are myriad and are various (hence getting a true estimate is really difficult).  Learning and exploring things in Linux is quite fascinating and exciting. Thanks to the hard work of millions of developers, who contributed to the development of Linux, and have made it reach the place where it is today.

In this post, I will be discussing some of the amazing facts, about Linux, that are lessor known to most of its users.