apache / apache/cassandra-gocql-driver

Database design

Open
#1,733 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
2.7k
Forks
658
PR merge metrics
No merged PRs in 30d

Description

I am working with Scylla for the first time. I have a very generic question. my usage is aboute storing and retriving sensor data. The question i have is:-

Would it make sense from a performance prespective to have one table per sensor - this would have a consequence of having 1000s of tables. OR

would it make sense to have one BIG table with million rows of data - this one table would be heavily read and written to.

any suggestions or thoughts would be highly appreciate.

Please answer these questions before submitting your issue. Thanks!

What version of Scalla are you using?
5.4.0

What version of Gocql are you using?
1.2.0

What version of Go are you using?
1.21.5

What did you do?

What did you expect to see?

What did you see instead?

---

Contributor guide

Open the contributing guide

Research direction

This is a general database-design question about storing and retrieving sensor data, not a defined change to the driver. No source file, test, or entry point is named, and the issue does not specify an actionable completion condition.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.