https://pconte.tech/categories/architecture/Recent content in Architecture on Patrick Contes blogHugo -- gohugo.ioen-usTue, 08 Jul 2025 22:00:32 +1000https://pconte.tech/p/designing-egress-in-aws/Tue, 08 Jul 2025 22:00:32 +1000https://pconte.tech/p/designing-egress-in-aws/ <h2 id="introduction">Introduction</h2> <p>AWS networking is fairly straightforward in a small setup. As a singular environment, you will generally have a single VPC that consists of:</p> <ul> <li>Subnets</li> <li>Route tables</li> <li>Network ACLs (NACLs)</li> <li>Security groups</li> <li>An Internet Gateway (IGW)</li> <li>NAT Gateway(s)</li> </ul> <p>There are other components, and even some of the ones mentioned here may not be required. You might have a single subnet for all of your resources. Likewise, a NAT Gateway may not even be necessary (this is rare — and anyone exposing private workloads to the internet unnecessarily is not following best practice).</p>https://pconte.tech/p/perfect-vs-practical-how-to-know-when-an-it-solution-is-ready/Thu, 12 Jun 2025 22:20:32 +1000https://pconte.tech/p/perfect-vs-practical-how-to-know-when-an-it-solution-is-ready/ <h2 id="introduction">Introduction</h2> <p>Designing IT solutions is a challenging task. Not only do you need to take several factors into consideration, but you also need to understand the lifecycle of what you’re designing. Questions will inevitably pop into your head, like:</p> <ul> <li>How long does this solution need to last?</li> <li>Is it going to be perpetual?</li> <li>How do we handle high availability and disaster recovery?</li> <li>When will I know it&rsquo;s complete?</li> </ul> <p>That last point—<em>when will I know it&rsquo;s complete?</em>—can be ambiguous. Does it mean the solution is fully fleshed out and working at the desired end state? Or does it mean it&rsquo;s ready once a Minimum Viable Product (MVP) has been constructed?</p>