From ad20a2dc2cdd5b4d13b6a88f18ef43736ae2ee9a Mon Sep 17 00:00:00 2001 From: Al Cutter Date: Wed, 4 Dec 2024 17:41:20 +0000 Subject: [PATCH] Tweak wording in getting started --- README.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index b9d38bc8..5cda366a 100644 --- a/README.md +++ b/README.md @@ -125,13 +125,18 @@ When writing your Tessera personality, the biggest decision you need to make fir * [POSIX](./storage/posix/) Each of these implementations has a very similar API, but they have different characteristics. + The easiest implementations to operate and to scale are the cloud implementations: GCP and AWS. -These are the recommended choice for the majority of users. +These are the recommended choice for the majority of users running in production. + +If you aren't using a cloud provider, then your options are MySQL and POSIX: +- POSIX is the simplest to get started with as it needs little in the way of extra infrastructure, and + if you already serve static files as part of your business/project this could be a good fit. +- Alternatively, if you are used to operating user-facing applications backed by a RDBMS, then MySQL could + be a natural fit. -If you aren't using a cloud provider, then your options are MySQL and POSIX. -POSIX is the more niche choice, intended to be lightweight and for logs that are infrequently updated. -If you already serve static files as part of your business this could be a good fit. -If you are more used to operating user-facing applications backed by a RDBMS, then MySQL will be a natural fit. +To get a sense of the rough performance you can expect from the different backends, take a look at +[docs/performance.md](/docs/performance). #### Setup