Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Top Level WHY VITESS Feature List #1217

Open
mattlord opened this issue Nov 8, 2022 · 2 comments
Open

Add Top Level WHY VITESS Feature List #1217

mattlord opened this issue Nov 8, 2022 · 2 comments
Assignees

Comments

@mattlord
Copy link
Collaborator

mattlord commented Nov 8, 2022

It's a fairly common perception in the market that Vitess is simply sharding middleware for MySQL. While sharding is certainly the flagship feature and the single biggest reason most people use Vitess, there are more and more features that make Vitess compelling even if you don't foresee the need to shard your database(s) anytime soon.

We should have a link to this page from the main website landing page. This also gives us a handy link for anyone wondering what Vitess offers and why they might want to use it -- even IF they don't need sharding (yet).

@deepthi
Copy link
Member

deepthi commented Jan 5, 2023

@mattlord can you take a look at https://vitess.io/docs/16.0/overview/whatisvitess/? It seems to cover this topic pretty well.
I do see that we are missing schema management and materialization in that feature list. We can add those.

@mattlord
Copy link
Collaborator Author

@mattlord can you take a look at https://vitess.io/docs/16.0/overview/whatisvitess/? It seems to cover this topic pretty well.
I do see that we are missing schema management and materialization in that feature list. We can add those.

In my mind anyway, these are related but different. That page is an overview of WHAT Vitess is (which is missing some things in that regard, as you noted). The other page would be WHY anyone might care about Vitess and WHY they might want to use it. There's certainly overlap on those two questions (WHAT and WHY) and I would be fine trying to combine the two. It will take a fair amount of work to do well though, I know having done my share of marketing-ish docs over the years. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants