vitess.io/vitess@v0.16.2/README.md (about)

     1  [![Maven Central](https://maven-badges.herokuapp.com/maven-central/io.vitess/vitess-jdbc/badge.svg)](https://maven-badges.herokuapp.com/maven-central/io.vitess/vitess-jdbc)
     2  [![Build Status](https://travis-ci.org/vitessio/vitess.svg?branch=master)](https://travis-ci.org/vitessio/vitess/builds)
     3  [![codebeat badge](https://codebeat.co/badges/51c9a056-1103-4522-9a9c-dc623821ea87)](https://codebeat.co/projects/github-com-youtube-vitess)
     4  [![Go Report Card](https://goreportcard.com/badge/vitess.io/vitess)](https://goreportcard.com/report/vitess.io/vitess)
     5  [![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2Fvitessio%2Fvitess.svg?type=shield)](https://app.fossa.io/projects/git%2Bgithub.com%2Fvitessio%2Fvitess?ref=badge_shield)
     6  [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/1724/badge)](https://bestpractices.coreinfrastructure.org/projects/1724)
     7  [![Coverage](https://sonarcloud.io/api/project_badges/measure?project=vitessio&metric=coverage)](https://sonarcloud.io/dashboard?id=vitessio)
     8  
     9  # Vitess 
    10  
    11  Vitess is a database clustering system for horizontal scaling of MySQL
    12  through generalized sharding.
    13  
    14  By encapsulating shard-routing logic, Vitess allows application code and
    15  database queries to remain agnostic to the distribution of data onto
    16  multiple shards. With Vitess, you can even split and merge shards as your needs
    17  grow, with an atomic cutover step that takes only a few seconds.
    18  
    19  Vitess has been a core component of YouTube's database infrastructure
    20  since 2011, and has grown to encompass tens of thousands of MySQL nodes.
    21  
    22  For more about Vitess, please visit [vitess.io](https://vitess.io).
    23  
    24  Vitess has a growing community. You can view the list of adopters
    25  [here](https://github.com/vitessio/vitess/blob/main/ADOPTERS.md).
    26  
    27  ## Reporting a Problem, Issue, or Bug
    28  To report a problem, the best way to get attention is to create a GitHub [issue](.https://github.com/vitessio/vitess/issues ) using proper severity level based on this [guide](https://github.com/vitessio/vitess/blob/main/SEVERITY.md). 
    29  
    30  For topics that are better discussed live, please join the [Vitess Slack](https://vitess.io/slack) workspace.
    31  You may post any questions on the #general channel or join some of the special-interest channels.
    32  
    33  Follow [Vitess Blog](https://blog.vitess.io/) for low-frequency updates like new features and releases.
    34  
    35  ## Security
    36  
    37  ### Reporting Security Vulnerabilities
    38  
    39  To report a security vulnerability, please email [vitess-maintainers](mailto:cncf-vitess-maintainers@lists.cncf.io).
    40  
    41  See [Security](SECURITY.md) for a full outline of the security process.
    42  
    43  ### Security Audit
    44  
    45  A third party security audit was performed by Cure53. You can see the full report [here](doc/VIT-01-report.pdf).
    46  
    47  ## License
    48  
    49  Unless otherwise noted, the Vitess source files are distributed
    50  under the Apache Version 2.0 license found in the LICENSE file.
    51  
    52  [![FOSSA Status](https://app.fossa.io/api/projects/git%2Bgithub.com%2Fvitessio%2Fvitess.svg?type=large)](https://app.fossa.io/projects/git%2Bgithub.com%2Fvitessio%2Fvitess?ref=badge_large)