Don't waste a whole bucket just for 'membership'

[pkese]

Couchbase buckets are a precious and rare resource.
Wasting a whole bucket just for a dozen membership records seems wrong.

Couldn't membership be implemented using couchbase datastructures?
https://blog.couchbase.com/net-core-list-queue-and-dictionary-data-structures-backed-by-couchbase/

[MikeGoldsmith]

Hi @pkese

Generally I agree, forcing a discreet bucket for membership would be a waste of resources. I think allowing it to be configurable would be best as each bucket could have different access control.

Would be good to have the membership bucket as a configurable property and I think managing them using data structures would be an interesting option.

[ashkan-saeedi-mazdeh]

Guys when I implemented this (in my first days of working woth couchbase), I didn't know buckets in couchbase are not equivalent to tables / collections in other databases. I thought they are more like a namespace but later on I realized that they are not meant to be used like this but I wanted to add all other Orleans services stuff like implementation of IReminderTable and IStatisticsProvider and geo-cluster

I agree that it is good to make this configurable.

Also keep in mind that when I was coding this some querying API didn't have any async versions so I called them inside Task.Run, If now they have sync versions, it is good to have them implemented using async versions instead of creating a new task.

[MikeGoldsmith]

@ashkan-saeedi-mazdeh

We are not trying to be critical of you, what you implemented initially was a great start and there is room for improvement.

Thanks for your input.

[ashkan-saeedi-mazdeh]

@MikeGoldsmith didn't take it personally at all :) I've made many wrong decisions when designing things which at the time seemed correct or due to time pressure just designed what I needed (just like everyone else). I encourage to criticize whatever I've don in this and also ask for changes or change whatever needs change.

I just provided the background because thought it might help. I was also thinking that if reminders become many then I might want to give the bucket for them more memory while for storage I don't want couchbase to have data in RAM since Orleans keeps hot data in RAM anyways, my choice not good for every case, so having this configurable as you suggested is the way.