Been torn between Postgres, Cassandra, and BoltDB for building this MVP, but A LOT of people are recommending DynamoDB. Thoughts?
-
-
(account management turns out to be non-trivial). I'd say go with Cass if you have a strongly time-series data requirement, 4/
-
or scale requirements from the get-go that you're sure Cass is a better fit for. Other go with PG. 5/5
-
Thanks Yehuda. :) I was thinking DynamoDB just because it's literally looking up books by ISBNs at the simplest form but...
-
PG would probably be the simplest thing to work with in this regard and fast to get up and running with.
-
All of this is coming from a Go service, so nothing too overly complex. Hoping to keep the service as lean and mean as possible.
-
PG works great as a simple key-value store, especially now that JSON is a first class value that can even be indexed.
-
but it sounds like you have a simple, small schema
-
Yeah, I'm going to try to make this schema as small and simple as possible. How many writes/sec can PG handle?
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.