C4 Model Diagram - Component

@startuml !include https://raw.githubusercontent.com/plantuml-stdlib/C4-PlantUML/master/C4_Component.puml title Component Diagram - Backend API ' --- External user --- Person(user, "End User") ' --- External containers (referenced, not redefined as components) --- ContainerDb(redis_store, "Redis", "In-memory cache", "Managed ElastiCache") ContainerDb(rds_store, "AWS RDS", "Relational DB", "PostgreSQL") ContainerDb(sf1_store, "Snowflake DB 1", "Data Warehouse", "Analytics") ContainerDb(sf2_store, "Snowflake DB 2", "Data Warehouse", "Analytics") ' --- Application boundary with components --- Container_Boundary(backend_container, "Backend API (ECS Fargate)") { Component(comp_api, "API Router", "Express/FastAPI", "Handles HTTP routing") Component(comp_user_svc, "User Service", "Business Logic", "Manages user operations") Component(comp_data_svc, "Data Service", "Business Logic", "Orchestrates data fetches") Component(comp_cache_mgr, "Cache Manager", "Utility", "Abstraction over Redis") Component(comp_rds_client, "RDS Client", "DAO", "Connects to RDS") Component(comp_sf_client, "Snowflake Client", "DAO", "Connects to Snowflake") } ' --- Frontend container (external to this component diagram) --- Container(frontend_container, "React Frontend", "S3 + CloudFront", "Static web app") ' --- Relationships --- Rel(user, frontend_container, "Uses", "HTTPS") Rel(frontend_container, comp_api, "Calls", "HTTPS") Rel(comp_api, comp_user_svc, "Delegates", "") Rel(comp_api, comp_data_svc, "Delegates", "") Rel(comp_data_svc, comp_cache_mgr, "Uses", "") Rel(comp_data_svc, comp_rds_client, "Fetches", "") Rel(comp_data_svc, comp_sf_client, "Queries", "") ' --- Component-to-external-container links --- Rel(comp_cache_mgr, redis_store, "Writes/Reads", "Redis Protocol") Rel(comp_rds_client, rds_store, "Executes", "SQL") Rel(comp_sf_client, sf1_store, "Queries", "Snowflake JDBC") Rel(comp_sf_client, sf2_store, "Queries", "Snowflake JDBC") @enduml

Comments

Post a Comment

Popular posts from this blog

AWS S3 MRAP

Image
  Amazon S3 Multi-Region Access Points In Simple terms, what is S3 MRAP? Imagine you have a giant box of toys (like S3 buckets) in different rooms (like different AWS regions) of your house (like the cloud). Normally, you'd have to remember which room each toy was in to find it. But with S3 MRAP, it's like having a magic label on the box that says "Toy Room" no matter which room it's actually in. You just say "Toy Room" and magically the label tells you the right room to go to! S3 MRAP is like a special label for your toy boxes (S3 buckets) that are spread out in different places (regions). You ask for a toy (data) using the label (MRAP endpoint), and the label tells you the best place (regional S3 bucket) to find it, no matter where it's stored! ~~Rakesh
Read more

SLO Compliance

SLO compliance refers to the extent to which a service meets or adheres to its defined Service Level Objectives (SLOs). An SLO is a specific, measurable target for a service's performance or reliability, such as uptime, response time, or error rate, agreed upon to ensure a certain level of quality for users. Compliance, in this context, means that the service is performing within the acceptable range or threshold set by the SLO over a specified period of time. For example, if an SLO states that a website should be available 99.9% of the time in a month, SLO compliance would be achieved if the actual availability meets or exceeds that 99.9% target. If it falls below, the service is considered non-compliant, which might trigger actions like alerts, investigations, or even penalties if tied to a Service Level Agreement (SLA) with customers. In practice, SLO compliance is tracked using Service Level Indicators (SLIs)—quantitative metrics like latency or success rate—that are monitored ...
Read more