<?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 Samantg on Medium]]></title>
        <description><![CDATA[Stories by Samantg on Medium]]></description>
        <link>https://medium.com/@samantg?source=rss-f036dfe4cd1a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*RhT5vT29NkyqMH1F</url>
            <title>Stories by Samantg on Medium</title>
            <link>https://medium.com/@samantg?source=rss-f036dfe4cd1a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:08:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@samantg/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 Think Like an AWS Solutions Architect (Beyond Certification)]]></title>
            <link>https://medium.com/@samantg/how-to-think-like-an-aws-solutions-architect-beyond-certification-e6e27f5398a9?source=rss-f036dfe4cd1a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6e27f5398a9</guid>
            <category><![CDATA[solution-architecture]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Samantg]]></dc:creator>
            <pubDate>Tue, 10 Feb 2026 12:36:02 GMT</pubDate>
            <atom:updated>2026-02-10T12:36:02.677Z</atom:updated>
            <content:encoded><![CDATA[<p>Most people think an AWS Solutions Architect is someone who knows a lot of AWS services.</p><p>In reality, <strong>a good AWS architect is not a service expert — they are a decision-maker.</strong></p><p>Passing the AWS Solutions Architect exam teaches you <em>what</em> services exist.<br> Real architecture work is about <strong>why</strong>, <strong>when</strong>, and <strong>what trade-offs</strong> you accept.</p><p>In this blog, I’ll share how I approach AWS architecture thinking in real projects — not exam questions.</p><h3>1. Start with the Problem, Not AWS Services</h3><p>A common mistake I see is this:</p><blockquote><em>“Should I use Lambda or ECS?”<br> “Is DynamoDB better than RDS?”</em></blockquote><p>These are <strong>wrong starting questions</strong>.</p><p>A Solutions Architect first asks:</p><ul><li>What problem are we solving?</li><li>Who are the users?</li><li>What is the expected traffic?</li><li>What is the business criticality?</li><li>What happens if the system goes down?</li></ul><p>Only after that do AWS services come into the picture.</p><p>👉 <strong>Architecture is business-driven, not service-driven.</strong></p><h3>2. Always Design for Failure (AWS Will Fail Too)</h3><p>One mindset shift every architect must make:</p><blockquote><strong><em>Everything will fail at some point.</em></strong></blockquote><ul><li>EC2 instances fail</li><li>AZs go down</li><li>Network latency happens</li><li>Deployments break</li></ul><p>AWS gives you building blocks, not guarantees.</p><p>That’s why architects think in terms of:</p><ul><li>Multi-AZ deployments</li><li>Load balancers</li><li>Auto Scaling</li><li>Health checks</li><li>Graceful degradation</li></ul><p>If your architecture assumes <em>“this will never fail”</em>, it’s already broken.</p><h3>3. Think in Layers, Not in Services</h3><p>Architects don’t memorize services — they think in <strong>layers</strong>.</p><p>Typical layers:</p><ul><li><strong>Presentation Layer</strong> (UI, CloudFront)</li><li><strong>Application Layer</strong> (EC2, ECS, Lambda)</li><li><strong>Data Layer</strong> (RDS, DynamoDB, S3)</li><li><strong>Caching Layer</strong> (Redis, CloudFront)</li><li><strong>Security Layer</strong> (IAM, WAF, Security Groups)</li></ul><p>Once layers are clear, choosing services becomes easy.</p><p>👉 <strong>Good architecture diagrams explain flow, not logos.</strong></p><h3>4. Trade-Off Thinking Is the Core Skill</h3><p>There is <strong>no perfect architecture</strong>.</p><p>Every decision has trade-offs:</p><ul><li>Cost vs Performance</li><li>Speed vs Security</li><li>Simplicity vs Scalability</li><li>Managed vs Control</li></ul><p>Example:</p><ul><li>Lambda reduces ops but increases cold-start risk</li><li>RDS is easy but limits extreme scale</li><li>DynamoDB scales infinitely but complicates queries</li></ul><p>A Solutions Architect’s job is to <strong>choose the right compromise</strong>, not the “best” service.</p><h3>5. Cost Is an Architectural Decision (Not Finance’s Problem)</h3><p>One of the biggest myths:</p><blockquote><em>“Cost optimization comes later.”</em></blockquote><p>Wrong.</p><p>Architecture decisions <em>define</em> cost:</p><ul><li>Chatty microservices = high data transfer cost</li><li>No caching = high compute cost</li><li>Over-provisioned EC2 = wasted money</li></ul><p>Architects must think:</p><ul><li>How will this scale cost-wise?</li><li>What happens at 10x traffic?</li><li>Can caching reduce load?</li><li>Is serverless justified here?</li></ul><p>👉 <strong>The cheapest service is the one you don’t call.</strong></p><h3>6. Security Is Not an Add-On</h3><p>Security is not:</p><blockquote><em>“We’ll add WAF later.”</em></blockquote><p>Security starts at architecture level:</p><ul><li>Public vs private subnets</li><li>Network boundaries</li><li>IAM least privilege</li><li>Data encryption</li><li>Blast radius control</li></ul><p>Architects design systems assuming:</p><ul><li>Credentials will leak</li><li>Someone will misconfigure</li><li>Traffic will be malicious</li></ul><p>AWS gives strong security tools — but <strong>only if architecture uses them correctly</strong>.</p><h3>7. Simple Architecture Beats Fancy Architecture</h3><p>A hard-earned lesson:</p><blockquote><strong><em>If two architectures solve the same problem, choose the simpler one.</em></strong></blockquote><p>Complexity:</p><ul><li>Increases operational burden</li><li>Slows down teams</li><li>Introduces hidden failure modes</li></ul><p>Microservices, event-driven systems, and serverless are powerful — but <strong>not mandatory</strong>.</p><p>Architects ask:</p><ul><li>Do we really need this complexity <em>now</em>?</li><li>Can we evolve later?</li></ul><h3>8. Think Evolution, Not Final State</h3><p>Good architects don’t design “final architecture”.</p><p>They design:</p><ul><li>A <strong>starting point</strong></li><li>A <strong>clear evolution path</strong></li></ul><p>Example:</p><ul><li>Start with a monolith</li><li>Add caching</li><li>Extract services gradually</li><li>Introduce async processing later</li></ul><p>👉 <strong>Architecture should enable change, not block it.</strong></p><h3>Final Thought</h3><p>An AWS Solutions Architect is:</p><ul><li>A translator between business and technology</li><li>A risk manager</li><li>A decision-maker</li><li>A simplifier</li></ul><p>AWS services will keep changing.<br> <strong>Architectural thinking will not.</strong></p><p>In the next blog, I’ll dive into:<br> 👉 <strong>Designing Highly Available Architectures on AWS (With Diagrams)</strong></p><p>If this helped you think differently about AWS architecture, give it a clap 👏<br> Follow for more real-world AWS architecture insights.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6e27f5398a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>