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

feat(database): setup initial vitess configurations #16

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

ihatelactose
Copy link

@ihatelactose ihatelactose commented Mar 17, 2023

Description 🎯

Vitess is a scalable cloud-native database layer that internally uses MySQL as database. However the layer created by Vitess makes MySQL sharding easier to do and use. It also manages the entire part of sharding and stuff. Which also means that this exposes only one mysql instance, therefore your application thinks its just talking to one mysqld instance!


Requirements 🤖

  • To make this work you must have minikube on your local machine (for Cloud the operator is provided)
  • To must allocate memory based on your requirement, for initial the requirements is set to absolute minimum (you need at the very least 8 GB of memory)
  • You must have docker installed since this works by default using docker runtime

Changes 📝

  • Added scripts for initializing Vitess cluster
  • Initial Vitess cluster configuration
  • Utility scripts for various utilities (feel free to use them without initial script too)

@ihatelactose ihatelactose changed the title feat: setup initial vitess configurations feat(database): setup initial vitess configurations Mar 17, 2023
@ihatelactose ihatelactose marked this pull request as draft March 17, 2023 13:55
@ihatelactose ihatelactose marked this pull request as ready for review March 18, 2023 16:19
@@ -0,0 +1,21 @@
#!/bin/bash

source ./utils.sh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please prefix the present working directory, else it assumes that I need to cd into the scripts directory

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done!

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

Successfully merging this pull request may close these issues.

2 participants