[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SEG9B96HP18ZJ0SN2PRY8":3,"skill-same:01M79SEG9B96HP18ZJ0SN2PRY8":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M79SEG9B96HP18ZJ0SN2PRY8","managed-databases-architect",null,"Architect-level managed database selection and operation — choosing between relational, document, key-value, and analytical engines, sizing and IOPS, multi-AZ and read replicas, connection pooling, backup and point-in-time recovery, and the operational limits of the managed tier. Use when a database is a cloud service rather than a server you run.","SriAkhilSJ\u002FPulseAIRepo","SriAkhilSJ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F206201543?v=4","01M79RWFD1Q09B89SXTTKKJY6Z","Sri Akhil SJ","01M79RWFE26NPG0BZ1FRNX376H",0,"MIT","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-and-devops-architect\u002Fdata-services-architect\u002Fmanaged-databases-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: managed-databases-architect\ndescription: Architect-level managed database selection and operation — choosing between relational, document, key-value, and analytical engines, sizing and IOPS, multi-AZ and read replicas, connection pooling, backup and point-in-time recovery, and the operational limits of the managed tier. Use when a database is a cloud service rather than a server you run.\nlicense: MIT\ncompatibility: RDS\u002FAurora, Cloud SQL, Azure SQL, DynamoDB, Cosmos, Firestore\nmetadata:\n  crusor-domain: cloud-and-devops-architect\n  crusor-path: cloud-and-devops-architect\u002Fdata-services-architect\u002Fmanaged-databases-architect\n  crusor-origin: original\n  crusor-sources: \"docs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide; cloud.google.com\u002Fsql\u002Fdocs; docs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide\"\n  crusor-triggers: \"rds, aurora, dynamodb, managed database, read replica, point in time recovery, connection pooling, database sizing, cloud sql, cosmos db\"\n  crusor-verified-on: \"2026-10-30\"\n---\n\n# Managed Databases Architect\n\nA managed database removes operations, not design. **Schema, access pattern, and\nconnection discipline are still yours**, and in some ways more consequential\nbecause you cannot tune the box.\n\n## When to use\n\n- Choosing a managed engine for a new service.\n- Performance or cost problems on RDS\u002FAurora\u002FCloud SQL\u002FDynamoDB.\n- Designing backups, replicas, or failover.\n\n## When NOT to use\n\n- Schema modelling detail → web `database-engineering-architect\u002F*`.\n- Self-managed clusters on Kubernetes → `kubernetes-architect` (and question the\n  choice).\n\n## Decision 1 — Engine\n\n| Need | Engine |\n|---|---|\n| relational, joins, transactions, known schema | PostgreSQL (often Aurora\u002FCloud SQL) |\n| relational, extreme read scale, storage growth | Aurora\u002FSpanner-class |\n| key-value at scale, predictable access by key | DynamoDB\u002FBigtable |\n| document, evolving schema, per-document queries | MongoDB\u002FCosmos\u002FFirestore |\n| analytical OLAP | warehouse, not OLTP engine |\n\n- Managed multi-model engines tempt you into one engine for everything; the\n  access-pattern mismatch shows up at scale, not at launch.\n- DynamoDB design is access-pattern-first: get the keys wrong and the fix is a\n  rewrite, not an index.\n\n## Decision 2 — Sizing\n\n- Size on the working set (fits in memory?) plus IOPS, not on row count.\n- Provision IOPS explicitly on gp3-style storage; default burst credits run out\n  under sustained load.\n- Serverless\u002Fon-demand tiers are for spiky, low-duty workloads; sustained load is\n  cheaper on provisioned capacity.\n- Measure p95 query latency and buffer cache hit ratio; both predict the wall.\n\n## Decision 3 — Availability\n\n- Multi-AZ for anything in the request path; understand the failover time\n  (seconds to minutes) and that connections drop.\n- Read replicas for read scale and for analytics isolation — not as a backup.\n- Failover tested; an untested failover is a guess about the app's retry logic.\n- Cross-region replicas for DR with a documented RPO and promotion runbook.\n\n## Decision 4 — Connections\n\n- The app's pool size × instance count must be below the database's max\n  connections. This is the single most common cloud outage.\n- Use a proxy\u002Fpooler (RDS Proxy, PgBouncer, Cloud SQL connector) for\n  serverless\u002Fbursty workloads.\n- Timeouts: connect, statement, idle — all set; a missing one becomes a stuck\n  service.\n- Long transactions block vacuum and locks; cap and alert on them.\n\n## Decision 5 — Backups\n\n- Automated backups with PITR enabled and retention matching the business.\n- Snapshots copied to another region\u002Faccount; test a restore, not just a backup.\n- Know the restore time: a 1 TB database is not a 5-minute operation.\n- Logical exports for reporting\u002Fportability alongside physical backups.\n\n## Decision 6 — Cost\n\n- Idle multi-AZ instances in dev; schedule them off.\n- Storage grows with WAL\u002Fbackups — set retention explicitly.\n- Reserved capacity for steady instances; on-demand for dev.\n- The expensive surprise is usually cross-AZ data transfer and replicas nobody\n  reads.\n\n## Failure modes at scale\n\n- 500 app connections from 20 Lambdas; database refuses connections under load.\n- Failover takes 90 s, app has no retry and no connection refresh.\n- Read replica used for writes in a reporting job, silently failing writes.\n- PITR off; a bad migration requires restoring a week-old snapshot.\n- DynamoDB table with one hot partition key; throttling in production only.\n\n## Verification receipts\n\n1. Engine choice with the access pattern it serves.\n2. Connection budget: pool × instances vs max connections, with headroom.\n3. Failover drill: connection loss handled, recovery time measured.\n4. Restore drill from PITR to a timestamp, verified data intact.\n5. Cost breakdown: instance, storage, IOPS, replicas, transfer.\n","# Managed Databases Architect\n\nA managed database removes operations, not design. **Schema, access pattern, and\nconnection discipline are still yours**, and in some ways more consequential\nbecause you cannot tune the box.\n\n## When to use\n\n- Choosing a managed engine for a new service.\n- Performance or cost problems on RDS\u002FAurora\u002FCloud SQL\u002FDynamoDB.\n- Designing backups, replicas, or failover.\n\n## When NOT to use\n\n- Schema modelling detail → web `database-engineering-architect\u002F*`.\n- Self-managed clusters on Kubernetes → `kubernetes-architect` (and question the\n  choice).\n\n## Decision 1 — Engine\n\n| Need | Engine |\n|---|---|\n| relational, joins, transactions, known schema | PostgreSQL (often Aurora\u002FCloud SQL) |\n| relational, extreme read scale, storage growth | Aurora\u002FSpanner-class |\n| key-value at scale, predictable access by key | DynamoDB\u002FBigtable |\n| document, evolving schema, per-document queries | MongoDB\u002FCosmos\u002FFirestore |\n| analytical OLAP | warehouse, not OLTP engine |\n\n- Managed multi-model engines tempt you into one engine for everything; the\n  access-pattern mismatch shows up at scale, not at launch.\n- DynamoDB design is access-pattern-first: get the keys wrong and the fix is a\n  rewrite, not an index.\n\n## Decision 2 — Sizing\n\n- Size on the working set (fits in memory?) plus IOPS, not on row count.\n- Provision IOPS explicitly on gp3-style storage; default burst credits run out\n  under sustained load.\n- Serverless\u002Fon-demand tiers are for spiky, low-duty workloads; sustained load is\n  cheaper on provisioned capacity.\n- Measure p95 query latency and buffer cache hit ratio; both predict the wall.\n\n## Decision 3 — Availability\n\n- Multi-AZ for anything in the request path; understand the failover time\n  (seconds to minutes) and that connections drop.\n- Read replicas for read scale and for analytics isolation — not as a backup.\n- Failover tested; an untested failover is a guess about the app's retry logic.\n- Cross-region replicas for DR with a documented RPO and promotion runbook.\n\n## Decision 4 — Connections\n\n- The app's pool size × instance count must be below the database's max\n  connections. This is the single most common cloud outage.\n- Use a proxy\u002Fpooler (RDS Proxy, PgBouncer, Cloud SQL connector) for\n  serverless\u002Fbursty workloads.\n- Timeouts: connect, statement, idle — all set; a missing one becomes a stuck\n  service.\n- Long transactions block vacuum and locks; cap and alert on them.\n\n## Decision 5 — Backups\n\n- Automated backups with PITR enabled and retention matching the business.\n- Snapshots copied to another region\u002Faccount; test a restore, not just a backup.\n- Know the restore time: a 1 TB database is not a 5-minute operation.\n- Logical exports for reporting\u002Fportability alongside physical backups.\n\n## Decision 6 — Cost\n\n- Idle multi-AZ instances in dev; schedule them off.\n- Storage grows with WAL\u002Fbackups — set retention explicitly.\n- Reserved capacity for steady instances; on-demand for dev.\n- The expensive surprise is usually cross-AZ data transfer and replicas nobody\n  reads.\n\n## Failure modes at scale\n\n- 500 app connections from 20 Lambdas; database refuses connections under load.\n- Failover takes 90 s, app has no retry and no connection refresh.\n- Read replica used for writes in a reporting job, silently failing writes.\n- PITR off; a bad migration requires restoring a week-old snapshot.\n- DynamoDB table with one hot partition key; throttling in production only.\n\n## Verification receipts\n\n1. Engine choice with the access pattern it serves.\n2. Connection budget: pool × instances vs max connections, with headroom.\n3. Failover drill: connection loss handled, recovery time measured.\n4. Restore drill from PITR to a timestamp, verified data intact.\n5. Cost breakdown: instance, storage, IOPS, replicas, transfer.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":31},{"crusor-path":25,"crusor-domain":26,"crusor-origin":27,"crusor-sources":28,"crusor-triggers":29,"crusor-verified-on":30},"cloud-and-devops-architect\u002Fdata-services-architect\u002Fmanaged-databases-architect","cloud-and-devops-architect","original","docs.aws.amazon.com\u002FAmazonRDS\u002Flatest\u002FUserGuide; cloud.google.com\u002Fsql\u002Fdocs; docs.aws.amazon.com\u002Famazondynamodb\u002Flatest\u002Fdeveloperguide","rds, aurora, dynamodb, managed database, read replica, point in time recovery, connection pooling, database sizing, cloud sql, cosmos db","2026-10-30","RDS\u002FAurora, Cloud SQL, Azure SQL, DynamoDB, Cosmos, Firestore","main","8fa4e240be65b98472c9b2d3a505ade2aea1a5c6","skills\u002Fcloud-and-devops-architect\u002Fdata-services-architect\u002Fmanaged-databases-architect","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ","Studying in CMR institute of Technology\r\n2024 - 2028","2026-11-13 21:02:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add SriAkhilSJ\u002FPulseAIRepo --skill managed-databases-architect",{"tool":45,"command":46},"bunx","bunx skills add SriAkhilSJ\u002FPulseAIRepo --skill managed-databases-architect",{"tool":48,"command":49},"pnpm","pnpm dlx skills add SriAkhilSJ\u002FPulseAIRepo --skill managed-databases-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fcloud-and-devops-architect\u002Fdata-services-architect\u002Fmanaged-databases-architect\u002FSKILL.md",true,[],[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M79TTAJNACCNXCEN3649CMMD","interaction-patterns-architect","Architect-level interaction design in code — choosing established patterns over invented ones, feedback and latency behaviour, destructive-action safeguards, navigation and overlay conventions, and the state model behind every interactive surface. Use when a screen has to behave, not just look.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Finteraction-patterns-architect\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79TT2ESKB1TKZBYY9KYJHV9","design-system-ops-architect","Architect-level operation of a design system in code — token pipelines and versioning, component API and variant policy, the catalogue as the contract, adoption metrics, and the governance that stops a system from forking into three. Use when a component library must survive several teams.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-system-ops-architect\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79TSV0PWGNK3PRX9P4JDR9N","design-handoff-architect","Architect-level design handoff — what must be specified before implementation starts, tokens over raw values, responsive and content-limit contracts, state matrices, and the review loop that catches drift between design and code. Use when a design is about to become code.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fdesign-handoff-architect\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79TSJS9BFXNP696FMJ9GKDA","content-microcopy-architect","Architect-level UI content — where strings live, voice and terminology consistency, error and empty-state copy as part of the interface, translation-ready authoring, and the content model a product needs before it multiplies screens. Use when the words in the interface matter as much as the pixels.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002Fcontent-microcopy-architect\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79TSCNBST3N1M68V1KPH9HQ","ui-ux-implementation-architect","Architect-level direction for turning a design into working UI — the handoff contract, component ownership versus screen-level layout, interaction and state conventions, design QA gates, and the review habits that keep an implementation faithful without frozen pixels. Use before any specific UI implementation skill.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Fui-ux-implementation-architect\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79TS4N6A4D2QQ433VXS5D0R","test-strategy-architect","Architect-level test strategy — allocating assertions across unit, integration, contract and end-to-end layers, designing for testability through dependency boundaries, fixture and data strategy, and the flake and coverage policies that keep a suite trustworthy. Use when defining how a codebase is tested.","https:\u002F\u002Fgithub.com\u002FSriAkhilSJ\u002FPulseAIRepo\u002Fblob\u002Fmain\u002Fskills\u002Fwebsite-architect\u002Ftesting-and-deployment-architect\u002Ftest-strategy-architect\u002FSKILL.md",[],[]]