6b3b2abe4f
73 stackexchange-grounded, 516 model-knowledge (ESCO-seeded gemma3), 0 review_needed (calibration caveat documented). Adapters rebuilt with the full competence sets; final REPORT numbers; all verify checks pass. Known gap: engineering-manager lacks an ESCO package counterpart. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PDKeXvpT6tENSvyQGLV1Uq
1.3 KiB
esco_uri, esco_label, relation, onet_soc, source, confidence, qa_count, generator, generated
| esco_uri | esco_label | relation | onet_soc | source | confidence | qa_count | generator | generated |
|---|---|---|---|---|---|---|---|---|
| http://data.europa.eu/esco/skill/7e796b51-49d7-4e73-95af-2e7323763f15 | design database in the cloud | optional | 15-1242.00 | model-knowledge | high | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
design database in the cloud — Database Administrator
For a Database Administrator, 'designing databases in the cloud' isn’t just about moving existing schemas to a cloud provider; it's fundamentally rethinking how you architect for resilience and scalability. Daily tasks shift from capacity planning for single servers to designing distributed systems – choosing between services like AWS Aurora/RDS, Azure SQL Database/Cosmos DB, or Google Cloud Spanner based on consistency requirements (ACID vs eventual), read/write patterns, and budget. You'll be heavily involved in defining replication strategies (multi-AZ deployments, cross-region replicas) and automated failover mechanisms from the start, not as an afterthought. This means understanding concepts like sharding, partitioning, and choosing appropriate data models for NoSQL options when traditional relational approaches don’t fit.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).