A production-grade, enterprise-ready, cloud-native key-value store backed by Slack.
Channel names are keys. The last message in the channel is the value. Immutable audit logging comes free with your Slack plan.
Redis costs money. Slack your company already pays for. This is arbitrage.
- Create a Slack app with a bot token (scopes:
channels:read,channels:manage,channels:history,chat:write) - Invite the bot to your workspace
- Export your token:
export SLACK_BOT_TOKEN=xoxb-...go build ./cmd/slackvalue
./slackvalue set my-key "hello world"
./slackvalue get my-key
# hello worldWrite throughput is bottlenecked by Slack's Tier 3 rate limit (1 message per second
per channel). Read throughput is bottlenecked by conversations.history pagination.
Multi-key transactions are left as an exercise for the reader (suggested approach:
bribe Slack to add MULTI/EXEC to their API).
Eventual consistency. Very eventual. Someone might be typing in your key right now.
Values are protected by Slack's enterprise-grade security model, plus whatever permissions your Slack admin forgot to revoke in 2019.
Is this a joke? The first rule of AI safety is to have fun.
Can I use this in production?
Do we work together?
|
┌────┴────┐
yes no
| |
please have
don't fun!
What about TTL? Slack's free plan deletes messages after 90 days. That's your TTL. You're welcome.