cockroach-staging / hello-world

0 stars 0 forks source link

S332: [EPIC]: As a prospective customer, I want a CockroachDB cluster created for me so that I can start using CockroachDB without having to worry about initial set up considerations like which cloud, which version etc. #594

Open exalate-issue-sync[bot] opened 4 years ago

exalate-issue-sync[bot] commented 4 years ago

[EPIC]: As a prospective customer, I want a CockroachDB cluster created for me so that I can start using CockroachDB without having to worry about initial set up considerations like which cloud, which version etc.

exalate-issue-sync[bot] commented 4 years ago

Rachel Casali commented: Need to validate this epic - some customers do have a preference for which cloud, so maybe they do want to worry about such decisions. For those customers, whats the thing that makes them choose this option?

  1. Which cloud do we use? does a customer even see that in v1? Eventually we want to show multiple cloud options (or not). Elastic shows GCP and AWS as options. a. region /AZs

  2. What are the technical menu options in creating a cluster? Which of these is reasonable for a customer to know and which are reasonable to even ask?

a. data size b. # of nodes - do we default to 3? do we even offer anything less than 3? do we even ask this? shouldn't it be our problem to figure it out? c. cores d. machine types (.e.g. if AWS M4, M3, M5 series) How much education do we do around these options vs how much do we pick as defaults? e. storage f. default enterprise features like encryption, backup auto enabled? g. do we have options for latency/ throughput? min max etc. how could we even measure that? h. high availability - option to be multi region

  1. What version of Cockroach will we run? Latest stable release?

  2. What sort of quick reference guide do we point to after this? Maybe some sort of docs ?

  3. Communication about what happens after this is created