Testing FDB on my local machine with the GO binding, very cool =)
I have 2 questions:
- About data modelling. In for example Cassandra and time series data it can be good to do a partition key as “userID::Activity::yy-mm-dd” rather than one wide row. In FBD can i use the subspace unlimited ? I mean can i create (“userID”, “Activity”) and (“UserID”, “Friends”) for every user (similiar to a “bucket”) or does it comes with a cost (other than storage) ? Does it make reads faster than store it in one big index with some kind of tuple/prefix ? (or it the sub/dir just a “wrapper” for prefixing the key anyway ?). In your docs about data modelling
you only use one subspace and let the key tuple describe the “path” or relationship instead of using multiple subspaces per path.
Take an example. A calendar where events are being stored per week (start/end date of the week) and the UI should populate these events onto the calendar. The request comes in with start/end date, does it seems ok to make subspaces of calendarID::weekDayStart::WeekDayEnd and store the individual events (event with date as key as well as counter for counting events for this week) in this subspace ?
- When you speak about multi-client/multi processes. Is this same as load balance the request (in the case of a web app) to multiple backends where each app is using it own DB connection (albeit shared in the between controllers in the app) ?