<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Engineering Blog</title>
    <link>https://engineering.yourcompany.com/</link>
    <description>Recent content on Engineering Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://engineering.yourcompany.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Getting Started with Docker for Web Development</title>
      <link>https://engineering.yourcompany.com/tutorials/docker-for-web-development/</link>
      <pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://engineering.yourcompany.com/tutorials/docker-for-web-development/</guid>
      <description>&lt;h1 id=&#34;getting-started-with-docker-for-web-development&#34;&gt;Getting Started with Docker for Web Development&lt;/h1&gt;&#xA;&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;Docker has become an essential tool for modern web development. It lets you package your application with all its dependencies into a standardized unit called a container, ensuring it runs consistently across any environment. In this tutorial, we&amp;rsquo;ll walk through the fundamentals of Docker and apply them to a real web development setup.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-docker&#34;&gt;What is Docker?&lt;/h2&gt;&#xA;&lt;p&gt;Docker is a platform for developing, shipping, and running applications in containers. Containers are lightweight, standalone executables that package code together with its runtime, system tools, libraries, and settings.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Optimizing Legacy Systems: A Case Study</title>
      <link>https://engineering.yourcompany.com/case-studies/optimizing-legacy-systems-case-study/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://engineering.yourcompany.com/case-studies/optimizing-legacy-systems-case-study/</guid>
      <description>&lt;h1 id=&#34;case-study-optimizing-legacy-systems-for-a-mid-market-enterprise&#34;&gt;Case Study: Optimizing Legacy Systems for a Mid-Market Enterprise&lt;/h1&gt;&#xA;&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Client:&lt;/strong&gt; Anonymous Manufacturing Company&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Industry:&lt;/strong&gt; Manufacturing / Supply Chain&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Project Duration:&lt;/strong&gt; 4 months&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Team Size:&lt;/strong&gt; 3 engineers&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Technologies:&lt;/strong&gt; Java 8 → Java 17, Spring Boot, PostgreSQL, Redis, Docker&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;the-challenge&#34;&gt;The Challenge&lt;/h2&gt;&#xA;&lt;p&gt;The client was running a 10-year-old Java application that handled their entire supply chain management. The system suffered from:&lt;/p&gt;&#xA;&lt;h3 id=&#34;business-context&#34;&gt;Business Context&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Legacy system causing 2-3 day delays in order processing&lt;/li&gt;&#xA;&lt;li&gt;Maintenance costs consuming 40% of IT budget&lt;/li&gt;&#xA;&lt;li&gt;Unable to integrate with modern e-commerce platforms&lt;/li&gt;&#xA;&lt;li&gt;Security vulnerabilities in outdated frameworks&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h3 id=&#34;technical-challenges&#34;&gt;Technical Challenges&lt;/h3&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Performance:&lt;/strong&gt; Page load times &amp;gt;8 seconds&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Scalability:&lt;/strong&gt; System crashed during peak seasonal demand&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Technical Debt:&lt;/strong&gt; 10,000+ lines of deprecated code&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Database:&lt;/strong&gt; Monolithic MySQL database with no indexing strategy&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Deployment:&lt;/strong&gt; Manual FTP uploads with no version control&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;our-solution&#34;&gt;Our Solution&lt;/h2&gt;&#xA;&lt;p&gt;We proposed a phased optimization approach rather than a complete rewrite, minimizing business disruption.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Modern Software Architecture: A Practical Guide</title>
      <link>https://engineering.yourcompany.com/architecture/modern-software-architecture-guide/</link>
      <pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate>
      <guid>https://engineering.yourcompany.com/architecture/modern-software-architecture-guide/</guid>
      <description>&lt;h1 id=&#34;modern-software-architecture-a-practical-guide&#34;&gt;Modern Software Architecture: A Practical Guide&lt;/h1&gt;&#xA;&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Modern software architecture has evolved rapidly in the last decade. Gone are the days of monolithic applications where every component was tightly coupled. Today&amp;rsquo;s architectures emphasize scalability, maintainability, and resilience.&lt;/p&gt;&#xA;&lt;p&gt;In this guide, we&amp;rsquo;ll walk through the key architectural patterns that define modern software development and help you choose the right approach for your project.&lt;/p&gt;&#xA;&lt;h2 id=&#34;key-architectural-patterns&#34;&gt;Key Architectural Patterns&lt;/h2&gt;&#xA;&lt;h3 id=&#34;1-microservices-architecture&#34;&gt;1. Microservices Architecture&lt;/h3&gt;&#xA;&lt;p&gt;Microservices break down applications into small, independent services that communicate over well-defined APIs.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
