Skip to content

Latest commit

 

History

History
30 lines (17 loc) · 1.97 KB

next-steps.md

File metadata and controls

30 lines (17 loc) · 1.97 KB
Raw

Next steps

  • Connect an existing database

    The tutorial above runs ReadySet against a sample database. To see the power of ReadySet against your own database, swap the upstream-db-url argument to point at an existing database for testing.

  • Connect your application

    Once you have a ReadySet instance up and running, the next step is to connect your application by swapping out your database connection string to point to ReadySet instead. The specifics of how to do this vary by database client library, ORM, and programming language. See Connect an App for examples.

    Note: By default, ReadySet will proxy all queries to the database, so changing your app to connect to ReadySet should not impact performance. You will explicitly tell ReadySet which queries to cache.

  • Cache queries

    Once ReadySet is proxying queries, connect a database SQL shell to ReadySet and use the custom SHOW PROXIED QUERIES SQL command to view the queries that ReadySet has proxied to your upstream database and identify which queries are supported by ReadySet. Then use the custom CREATE CACHE SQL command to cache supported queries.

    Note: To successfully cache the results of a query, ReadySet must support the SQL features and syntax in the query. For more details, see SQL Support.

  • Tear down

    When you are done testing, stop and remove the Docker resources:

    docker rm -f readyset postgres mysql \
&& docker volume rm readyset

  • Additional deployment options In addition to Docker, you can deploy ReadySet using binaries. For Kubernetes environments, check out how to deploy ReadySet to Kubernetes.