What problem does it solve? Go developers at ByteDance often struggle to find correct initialization patterns, configuration parameters, and best practices when integrating internal storage and messaging services like RDS, Redis, Abase, TOS, EventBus, BMQ, RocketMQ, ByteES, ByteGraph, ByteKV, and VikingDB. This Skill consolidates SDK usage guides, code examples, and common pitfalls into one knowledge base. ## Core Features & Use Cases - SDK Selection Guidance: Maps each storage service (RDS/MySQL, Redis, Bytedoc/MongoDB, Abase, TOS, EventBus, BMQ, RocketMQ, ByteES, ByteGraph, ByteKV, VikingDB) to its correct Go SDK package and initialization pattern. - Ready-to-Use Code Snippets: Provides initialization, CRUD, transaction, batch, and query examples for each SDK, including connection pool and timeout configuration. - Pitfall Avoidance: Documents known limitations such as Abase's lack of Lua script support, ByteKV's 100KB value size limit, and BMQ's 20MB message size cap. - Use Case: When you need to add Abase caching to a Go microservice, this Skill tells you to use goredis with NewAbaseClientWithOption, set IdleTimeout below 30 minutes, and avoid SDK-level retries. ## Quick Start Ask how to connect to a specific ByteDance storage service in Go, for example: show me how to initialize a ByteKV client and perform a CAS update.
