<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Projects on Brent Hollers</title><link>https://brenthollers.com/categories/projects/</link><description>Recent content in Projects on Brent Hollers</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 06 Jan 2026 22:55:05 -0400</lastBuildDate><atom:link href="https://brenthollers.com/categories/projects/index.xml" rel="self" type="application/rss+xml"/><item><title>From On-Prem to Cloud-Native: A Federal Migration &amp; Modernization Journey</title><link>https://brenthollers.com/projects/</link><pubDate>Tue, 06 Jan 2026 22:55:05 -0400</pubDate><guid>https://brenthollers.com/projects/</guid><description>&lt;h3 id="objective"&gt;Objective&lt;/h3&gt;
&lt;p&gt;To develop a more concrete understanding of modernization and migration strategies for complex systems which also has specific security, resiliency, and accessibility requirements, I chose to simulate a realistic Federal Cloud Transformation scenario—migrating a legacy, stateful mission application from an on-premise data center to AWS, and subsequently refactoring it into a secure, scalable, cloud-native architecture on Kubernetes.
The Scenario:
A federal agency is running a critical &amp;ldquo;Mission Status&amp;rdquo; application on aging on-premise hardware (Dell PowerEdge/VMware). The agency has a mandate to evacuate the data center (Cloud First Policy) and improve the application&amp;rsquo;s security posture and scalability (Modernization).&lt;/p&gt;</description></item></channel></rss>