Devops

Other Parts of This Series: Part 25: DevOps - Step By Step Learning : Part 25 (Docker Networking With Help Of Linux Namespace) DevOps Build Tools (Photo Credit: Unsplash) Story: Rasel observed some of his junior software developer colleagues limited to an IDE. This means they were skilled at writing code and running it with a single click of the IDE’s run button. But they didn’t know how the code was built on the server side. They should know beyond the IDE, as the server has no IDE or run buttons at all. So Rasel decided to assist them in understanding the build tools, how they work, and their importance. ...

Other Parts of This Series: Part 24: DevOps - Step By Step Learning : Part 24 (Docker Compose & Docker Swarm Hands On) Part 26: DevOps - Step By Step Learning : Part 26 (Build Tools and Its Necessity) DevOps Docker Networking (Photo Credit: Unsplash) Story: Rasel learned the fundamentals of native Docker, Docker Compose, and Docker Swarm. And by doing so, he solved the consistency and ‘it works on my machine’ issues in his daily development life. ...

Other Parts of This Series: Part 23: DevOps - Step By Step Learning : Part 23 (Docker Hands On) Part 25: DevOps - Step By Step Learning : Part 25 (Docker Networking With Help Of Linux Namespace) DevOps Docker Compose & Docker Swarm (Photo Credit: Unsplash) Story: Pure Docker is useful for running a simple standalone application or service. But real-world projects are not always as straightforward and simple as they appear. During development, we constantly require multiple dependencies or services to function, such as a database, cache, message broker, and so on. Rasel realized we needed something to solve this problem. Rasel was looking for a solution that was capable of handling multiple container bootstrapping. And guess what? Rasel discovered that Docker Compose is the solution. That’s why, Rasel decided to learn Docker Compose and Docker Swarm in detail. ...

Other Parts of This Series: Part 22: DevOps - Step By Step Learning : Part 22 (Introduction of Containerization Tool Docker) Part 24: DevOps - Step By Step Learning : Part 24 (Docker Compose & Docker Swarm Hands On) DevOps Docker Containerization (Photo Credit: Unsplash) Story: Understanding what containerization is, why it is necessary, and how it works is critical before delving into Docker or any other container tools (like: podman, containerd etc.). Rasel wanted to go hands-on with Docker after understanding these concepts. So, as planned, Rasel begins with the Docker architecture and basic commands that needs for his day-to-day development. And gradually move to the advanced concepts of Docker. ...

Other Parts of This Series: Part 20: DevOps - Step By Step Learning : Part 20 (Hands On Networking Commands, Practically Connect The Theory) Part 23: DevOps - Step By Step Learning : Part 23 (Docker Hands On) DevOps Docker Containerization (Photo Credit: Unsplash) Story: Rasel felt more comfortable and confident after learning the fundamentals. Now he thought it was time to start learning DevOps tools. But where should he start? There are numerous tools that are commonly used in DevOps practice. Then he made the decision to start with Docker. Because as a software engineer he faced numerous challenges when installing, running, and building software and its dependencies. And the well-known issue “It works on my machine” always arises. As far as he knew, Docker, or container technology, solved this type of problem. That is why he decided to learn containerization first. ...

Other Parts of This Series: Part 19: DevOps - Step By Step Learning : Part 19 (TCP and UDP Are The Backbone of Transport Layer) Part 22: DevOps - Step By Step Learning : Part 22 (Introduction of Containerization Tool Docker) DevOps Networking Practical (Photo Credit: Unsplash) Story: Rasel now wanted to explore and practice the learned theoretical data communication and networking concepts hands-on. He wanted to practically capture as much information as possible about host-to-host packet transfer of each layer of the OSI model using Linux commands. From the high level, Rasel started from the below point: ...

Other Parts of This Series: Part 18: DevOps - Step By Step Learning : Part 18 (NAT, PAT For Inner Private with Outer Public Network Handshaking) Part 20: DevOps - Step By Step Learning : Part 20 (Hands On Networking Commands, Practically Connect The Theory) DevOps Networking TCP & UDP (Photo Credit: Unsplash) Story: Till now Rasel explored how data move host to host over the OSI or TCP/IP model by utilizing all the parties/parts like networking devices and protocols. He understood how source and destination IPs resolved in the application layer using DHCP and DNS, respectively. Also, he tried to realize how the logical address, like IP, makes a connection with the physical address, like the MAC address, using ARP the bridge between the data link and network layers. Besides all of these, Rasel explored how do using mechanisms like NAT/PAT overcome IPv4 limitations and private-public IP mapping in the transport and network layers. All the points were served via MAC address table, routing table, ARP table/cache, NAT mapping table, etc. ...

Other Parts of This Series: Part 17: DevOps - Step By Step Learning : Part 17 (ARP Is The Bridge Between Data Link and Network Layer) Part 19: DevOps - Step By Step Learning : Part 19 (TCP and UDP Are The Backbone of Transport Layer) DevOps Networking NAT & PAT (Photo Credit: Unsplash) Story: Rasel found that the one and only unique need to communicate with each other throughout the internet is an IP address. Every host/device needs a universally unique IP address so that routing can be possible from source to destination. Also, while Rasel played with packet tracing and IP addresses, he observed that the inner and outer IPs were not the same. When a packet passes through the router to the internet, then an IP change happens. Besides this, the most used IP address scheme is IPv4, which has 4 bytes or 32 bits, and the universally unique IP can be 2^32 or ~4.2 billion IP addresses. But as the Internet grew in popularity, the industry realized there would one day be more hosts on the Internet than there were IP addresses available. So IPv6 was created, but it is complex and not mostly used. So Rasel wanted to know the magic behind this IP changing. ...

Other Parts of This Series: Part 16: DevOps - Step By Step Learning : Part 16 (How DNS and DHCP Operates in Application Layer) Part 18: DevOps - Step By Step Learning : Part 18 (NAT, PAT For Inner Private with Outer Public Network Handshaking) DevOps Networking ARP (Photo Credit: Unsplash) Story: After exploring the source and destination IP resolution process in application layer using DNS and DHCP, Rasel now wanted to explore in low level how this IP is actively used in other layers. He observed that an IP address is the logical addressing scheme for nodes on a network. IP addresses exist at the Network layer of the OSI Model and help facilitate the L3 goal of “end to end” delivery. On the other hand, a MAC address is the physical addressing scheme for individual NIC cards on each node of a network. MAC addresses exist at the Data Link layer of the OSI Model and help facilitate the L2 goal of “hop to hop” delivery. But in this point, Rasel was every curious to know the depth process how this 2 logical and physical addressing correlate with each other. ...

Other Parts of This Series: Part 15: DevOps - Step By Step Learning : Part 15 (Learn Fundamental Networking Theoretical Knowledge) Part 17: DevOps - Step By Step Learning : Part 17 (ARP Is The Bridge Between Data Link and Network Layer) DevOps Networking DNS & DHCP (Photo Credit: Unsplash) Story: Rasel learned the basic theoretical networking knowledge. He also understood how all the communication works by combining different important parts from the high level. But he was also curious to know the low level. First he wanted to start from the application layer (Layer 7 in OSI, Layer 4 in the TCP/IP model). He learned that the source and destination IP are resolved in the application layer and those used in other layers, like the session layer and so on. Now he was genuinely interested in how this source and destination IP resolving works behind the scenes in detail. Thus Rasel deep dives in exploring. ...