<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Temitope Aluko on Medium]]></title>
        <description><![CDATA[Stories by Temitope Aluko on Medium]]></description>
        <link>https://medium.com/@damilotunaluko?source=rss-fa71b8c75052------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZQneJklpZg5fuqZhRJkq5w@2x.jpeg</url>
            <title>Stories by Temitope Aluko on Medium</title>
            <link>https://medium.com/@damilotunaluko?source=rss-fa71b8c75052------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 05:47:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@damilotunaluko/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[HOW TO INSTALL DOCKER ENGINE ON UBUNTU EC2 SERVER]]></title>
            <link>https://medium.com/@damilotunaluko/how-to-install-docker-engine-on-ubuntu-ec2-server-9de461feb8a3?source=rss-fa71b8c75052------2</link>
            <guid isPermaLink="false">https://medium.com/p/9de461feb8a3</guid>
            <dc:creator><![CDATA[Temitope Aluko]]></dc:creator>
            <pubDate>Fri, 07 Jun 2024 12:01:41 GMT</pubDate>
            <atom:updated>2024-06-07T12:01:41.626Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*6uRZSFdvQDmZfokFhFB2XQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/342/1*RJSydL08kyJhDwAfnxnTsw.png" /></figure><p>💡 Docker Engine depends on containerd and runc. Docker Engine bundles these dependencies as one bundle: containerd.io. If you have installed the containerd or runc previously, uninstall them to avoid conflicts with the versions bundled with Docker Engine.</p><p>Run the following command to uninstall all conflicting packages:</p><pre>for pkg in docker.io docker-doc docker-compose docker-compose-v2 podman-docker containerd runc; do sudo apt-get remove $pkg; done</pre><h3><a href="https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository">Install using the apt repository</a></h3><p>Before you install Docker Engine for the first time on a new host machine, you need to set up the Docker repository. Afterward, you can install and update Docker from the repository.</p><ol><li>Set up Docker’s apt repository.</li></ol><pre># Add Docker&#39;s official GPG key:<br>sudo apt-get update<br>sudo apt-get install ca-certificates curl<br>sudo install -m 0755 -d /etc/apt/keyrings<br>sudo curl -fsSL &lt;https://download.docker.com/linux/ubuntu/gpg&gt; -o /etc/apt/keyrings/docker.asc<br>sudo chmod a+r /etc/apt/keyrings/docker.asc<br><br># Add the repository to Apt sources:<br>echo \\<br>  &quot;deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] &lt;https://download.docker.com/linux/ubuntu&gt; \\<br>  $(. /etc/os-release &amp;&amp; echo &quot;$VERSION_CODENAME&quot;) stable&quot; | \\<br>  sudo tee /etc/apt/sources.list.d/docker.list &gt; /dev/null<br>  sudo apt-get update</pre><p>2. Install the Docker packages.</p><p>To install the latest version, run:</p><pre>sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin</pre><p>3. Verify that the Docker Engine installation is successful by running the hello-world image.</p><pre>sudo docker run hello-world</pre><p>💡Hello from Docker! This message shows that your installation appears to be working correctly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9de461feb8a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Load Balancer vs. Nginx: Choosing the Right Tool for Deployment]]></title>
            <link>https://medium.com/@damilotunaluko/load-balancer-vs-nginx-choosing-the-right-tool-for-deployment-ec80d552d132?source=rss-fa71b8c75052------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec80d552d132</guid>
            <dc:creator><![CDATA[Temitope Aluko]]></dc:creator>
            <pubDate>Thu, 05 Oct 2023 21:44:32 GMT</pubDate>
            <atom:updated>2023-10-05T21:44:32.721Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Introduction:</strong></h3><p>When it comes to deploying web applications, ensuring high availability, scalability, and efficient traffic distribution is paramount. Load balancing is a crucial component of this process, and two popular solutions for this purpose are Load Balancers and Nginx. In this article, I’ll explore the key differences between them and help you determine which one is the best fit for your deployment needs. Additionally, I’ll discuss the benefits they bring to your application.</p><h3>Load Balancer:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LkUozYf5laXQLoGZp9OejA.jpeg" /></figure><ol><li><strong>Functionality:</strong> Load balancers are dedicated appliances or software solutions designed specifically to distribute network traffic across multiple servers or instances. They distribute incoming requests based on various algorithms like round-robin, least connections, or IP hash.</li><li><strong>Scalability: </strong>Load balancers are excellent at horizontal scaling, allowing you to add or remove backend servers seamlessly. This makes them ideal for large-scale applications with fluctuating traffic patterns.</li><li><strong>High Availability: </strong>Load balancers can provide high availability by routing traffic to healthy servers, reducing the risk of server failures affecting your application’s uptime.</li><li><strong>Load Distribution: </strong>Load balancers evenly distribute incoming requests, preventing any single server from being overwhelmed. This ensures efficient resource utilization.</li><li><strong>Security: </strong>Some load balancers offer advanced security features, such as DDoS protection, SSL termination, and Web Application Firewall (WAF) capabilities.</li></ol><h3>Nginx:</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/964/1*PVqWGDjMEuiyNIUeXLLnpg.png" /></figure><ol><li><strong>Functionality: </strong>Nginx is a versatile web server and reverse proxy server. While it is not solely a load balancer, it can be configured to perform load balancing tasks efficiently.</li><li><strong>Scalability:</strong> Nginx is highly scalable and lightweight, making it a suitable choice for applications that need to handle a large number of concurrent connections.</li><li><strong>High Availability:</strong> Nginx can be used in conjunction with other tools to achieve high availability. For example, you can set up Nginx as a reverse proxy in front of multiple application servers, providing a level of fault tolerance.</li><li><strong>Load Distribution:</strong> Nginx offers various load balancing methods, including round-robin, least connections, and IP hash. It allows you to fine-tune load balancing based on your application’s requirements.</li><li><strong>Flexibility: </strong>Nginx is known for its flexibility and extensibility. It can serve as a web server, reverse proxy, and load balancer simultaneously, providing a single point of control for multiple functions.</li></ol><p><strong>Load Balancer Benefits:</strong></p><ul><li><strong>Improved Scalability</strong>: Load balancers enable you to add or remove servers dynamically, accommodating increased traffic.</li><li><strong>High Availability</strong>: They enhance application uptime by distributing traffic to healthy servers.</li><li><strong>Efficient Resource Utilization</strong>: Load balancers prevent server overload, ensuring optimal performance.</li></ul><p><strong>Nginx Benefits:</strong></p><ul><li><strong>Versatility</strong>: Nginx serves as both a web server and a reverse proxy, offering more than just load balancing.</li><li><strong>Performance</strong>: Its lightweight design and efficient event-driven architecture make it highly performant.</li><li><strong>Flexibility</strong>: Nginx can be tailored to your application’s unique needs, making it suitable for a wide range of use cases.</li></ul><p><strong>Conclusion</strong>: Choosing between a dedicated Load Balancer and Nginx for your deployment depends on your application’s specific requirements. Load balancers excel at distributing traffic in large-scale, mission-critical applications. In contrast, Nginx offers versatility and efficiency, making it a compelling choice for many scenarios. Consider your application’s size, scalability needs, and desired features to make an informed decision on which tool to use for your deployment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec80d552d132" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Comprehensive Guide to Creating Docker Images for Node.js Applications and Running Containers]]></title>
            <link>https://medium.com/@damilotunaluko/a-comprehensive-guide-to-creating-docker-images-for-node-js-applications-and-running-containers-b53ad60da3ca?source=rss-fa71b8c75052------2</link>
            <guid isPermaLink="false">https://medium.com/p/b53ad60da3ca</guid>
            <dc:creator><![CDATA[Temitope Aluko]]></dc:creator>
            <pubDate>Sat, 23 Sep 2023 14:04:52 GMT</pubDate>
            <atom:updated>2023-09-23T14:04:52.175Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/324/1*jll1ZjpQ9DsODfJ4_KPLrQ.png" /></figure><p>If you’re a developer looking to streamline your application deployment and make it more efficient, Docker is your go-to solution. Docker allows you to package your application and its dependencies into a single unit called a container, ensuring that it runs consistently across different environments. In this comprehensive guide, we’ll walk you through the process of creating a Docker image for a Node.js application and running it as a container. Let’s dive in!</p><p><strong>Step 1: Install Docker</strong></p><p>Before we start, ensure that you have Docker installed on your system. You can download and install Docker from the official website (https://www.docker.com/get-started).</p><p><strong>Step 2: Set Up Your Node.js Application</strong></p><p>Assuming you have a Node.js application ready, create a directory for your project if you haven’t already and place your application files inside it. Your project structure might look something like this:</p><p><strong>my-node-app/</strong></p><p>├── package.json</p><p>├── server.js</p><p>└── …</p><p><strong>Step 3: Dockerfile — The Blueprint</strong></p><p>The Dockerfile is a crucial component in creating a Docker image. It contains instructions for Docker on how to build your image. Create a file named `Dockerfile` in your project directory with the following content:</p><h3><strong>Dockerfile</strong></h3><pre># Use an official Node.js runtime as a parent image<br>FROM node:14<br># Set the working directory in the container<br>WORKDIR /usr/src/app<br># Copy package.json and package-lock.json to the working directory<br>COPY package*.json ./<br># Install application dependencies<br>RUN npm install<br># Copy your application code into the container<br>COPY . .<br># Expose a port your application will listen on<br>EXPOSE 3000<br># Define the command to run your application<br>CMD [&quot;node&quot;, &quot;server.js&quot;]</pre><blockquote>This Dockerfile does the following:</blockquote><blockquote>- Starts with an official Node.js image.</blockquote><blockquote>- Sets the working directory.</blockquote><blockquote>- Copies your `package.json` and `package-lock.json` files and installs dependencies.</blockquote><blockquote>- Copies your application code into the container.</blockquote><blockquote>- Exposes port 3000 (you can change this if your app uses a different port).</blockquote><blockquote>- Defines the command to run your Node.js application.</blockquote><p><strong>Step 4: Build Your Docker Image</strong></p><p>Open a terminal, navigate to your project directory, and run the following command to build your Docker image (don’t forget the dot at the end):</p><pre>docker build -t my-node-app .</pre><p>The `-t` flag allows you to tag your image with a name (e.g., `my-node-app`).</p><p><strong>Step 5: Run Your Docker Container</strong></p><p>With the Docker image created, you can now run your Node.js application in a container:</p><pre>docker run -p 3000:3000 my-node-app</pre><p>This command maps port 3000 in your container to port 3000 on your host machine. You can access your Node.js application at `http://localhost:3000`.</p><p><strong>Step 6: Managing Your Containers</strong></p><p>To view a list of running containers, use:</p><pre>docker ps</pre><p>To stop a running container, use:</p><pre>docker stop &lt;container_id&gt;</pre><p>And to remove a container (after stopping it), use:</p><pre>docker rm &lt;container_id&gt;</pre><p><strong>Conclusion</strong></p><p>Congratulations! You’ve successfully created a Docker image for your Node.js application and ran it as a container. Docker simplifies the deployment process, making it easier to manage dependencies and ensure consistent environments across different platforms. This comprehensive guide should help you get started with Dockerizing your Node.js applications. Happy coding and containerizing! 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b53ad60da3ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>