Methodology for Selecting Purpose-Built AWS Services

This study guide focuses on the structured process of evaluating and selecting specialized AWS services to optimize performance, cost, and scalability, aligning with the AWS Certified Solutions Architect - Professional (SAP-C02) requirements.

Learning Objectives

By the end of this module, you should be able to:

• Evaluate compute platforms based on abstraction levels and modernization scope.
• Identify opportunities for decoupling using appropriate application integration services.
• Select purpose-built databases based on access patterns and data structures.
• Determine the optimal storage service for specific performance and durability needs.
• Formulate a modernization strategy (Re-host, Re-platform, Re-factor) for legacy workloads.

Key Terms & Glossary

• Purpose-Built Service: A service designed specifically to excel at a particular task (e.g., DynamoDB for high-scale NoSQL) rather than a general-purpose tool.
• Decoupling: The practice of separating application components so they can evolve, scale, and fail independently.
• Serverless: A cloud execution model where the provider manages the server infrastructure, automatically scaling and charging only for actual usage.
• Orchestration: A centralized method of coordinating multiple services (e.g., AWS Step Functions) to manage complex workflows.
• Choreography: A decentralized approach where services communicate via events (e.g., Amazon EventBridge) without a central coordinator.

The "Big Idea"

The transition from monolithic architectures to cloud-native systems is defined by the shift from "One Size Fits All" to "The Right Tool for the Job." A robust selection methodology prevents "technical debt" by ensuring that a service's characteristics (e.g., latency, throughput, consistency) align precisely with the business requirement. Instead of forcing a relational database to handle high-frequency key-value lookups, a professional architect selects a purpose-built NoSQL engine, thereby optimizing both performance and cost.

Formula / Concept Box

Hierarchical Outline

1. Compute Selection Methodology
   • Virtual Machines (EC2): Full control, manual scaling, high operational overhead.
   • Managed Containers (ECS/EKS): High portability, balanced control and management.
   • Serverless (Lambda/Fargate): Zero server management, event-driven, fastest time-to-market.
2. Database Strategy
   • Relational (Aurora): Complex joins, ACID compliance, structured data.
   • NoSQL (DynamoDB): Millisecond latency at any scale, predictable performance.
   • In-Memory (ElastiCache): Sub-millisecond latency for session state and caching.
3. Application Integration Patterns
   • Point-to-Point (API Gateway): Synchronous, request-response.
   • Asynchronous (SQS/SNS): Buffering and fan-out to prevent cascading failures.
   • Event-Driven (EventBridge): Seamless integration of 3rd party and internal events.
   • Stateful Workflows (Step Functions): Visual orchestration of distributed components.

Visual Anchors

Compute Decision Flow

The Abstraction vs. Control Spectrum

\begin{tikzpicture}[scale=0.8] \draw[thick,->] (0,0) -- (10,0) node[anchor=north] {Management Abstraction (High)}; \draw[thick,->] (0,0) -- (0,6) node[anchor=east] {Control/Customization (High)}; \filldraw[blue] (1,5) circle (2pt) node[anchor=west] {EC2}; \filldraw[orange] (4,3.5) circle (2pt) node[anchor=west] {ECS/EKS}; \filldraw[red] (7,2) circle (2pt) node[anchor=west] {Fargate}; \filldraw[purple] (9,0.5) circle (2pt) node[anchor=west] {Lambda}; \draw[dashed] (0,6) -- (10,0); \end{tikzpicture}

Definition-Example Pairs

• Service: Amazon SQS
  • Definition: A fully managed message queuing service that enables you to decouple and scale microservices, distributed systems, and serverless applications.
  • Real-World Example: An e-commerce site uses SQS to hold order information. The frontend places the order in the queue, and a backend service processes it as capacity allows, ensuring the frontend stays responsive during traffic spikes.
• Service: AWS Step Functions
  • Definition: A low-code visual workflow service used to orchestrate AWS services, automate business processes, and build serverless applications.
  • Real-World Example: An insurance company uses Step Functions to manage a claims process that involves image analysis (Rekognition), data entry (Lambda), and human approval steps.

Worked Examples

Scenario: Modernizing a Legacy Three-Tier App

Problem: A company has a monolithic Ruby on Rails app on EC2 that struggles with scaling during sales and has a single MySQL database that is reaching its IOPS limit.

Methodology Application:

1. Compute: Decompose the monolith into microservices. Move the core API to Amazon ECS with Fargate to remove server management while maintaining container consistency.
2. Database: Migrate the relational data to Amazon Aurora with Read Replicas to handle high read traffic. Move the session data and shopping cart to Amazon DynamoDB for sub-second performance.
3. Integration: Use Amazon SQS to decouple the "Order Completion" logic from the "Email Notification" logic to ensure emails don't block the checkout process.

Checkpoint Questions

1. When should you choose Amazon EventBridge over Amazon SNS for event routing?
2. Which compute service is best for a task that requires sub-millisecond execution but involves 20GB of temporary local storage?
3. True or False: Amazon RDS is considered a serverless service in all its configurations.
4. What is the primary benefit of using AWS Step Functions for long-running processes compared to Lambda alone?
5. In what scenario would you prefer Amazon MQ over Amazon SQS?

Muddy Points & Cross-Refs

[!TIP] Confusion: SQS vs. SNS vs. EventBridge

• SQS is for Pull (One-to-One). Use when you need a buffer.
• SNS is for Push (One-to-Many). Use for high-throughput broadcast.
• EventBridge is for Schema-based Routing. Use for complex filtering and 3rd party SaaS integration.

[!WARNING] Lambda Limits: Remember the 15-minute execution limit. For tasks longer than this, always pivot to ECS/Fargate or Step Functions.

Comparison Tables

Compute Platform Comparison

Database Use-Case Matrix