From 372f943989413c5dfadfa56ea35b1e8685b3ea21 Mon Sep 17 00:00:00 2001 From: Evgheni Date: Wed, 17 Apr 2024 17:25:46 +0300 Subject: [PATCH] added roadmap checkboxes to readme --- README.md | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/README.md b/README.md index b01d7c4..f32e757 100644 --- a/README.md +++ b/README.md @@ -16,23 +16,23 @@ The color of each element in the diagram indicates whether the element is part o The following sections provide recommendations and considerations for each section of the Commerce Reference Architecture diagram. ## Varnish -- A Varnish cluster can scale to the traffic of a site -- Tune the instance size based on the number of cache pages needed -- On a high-traffic site, use a Varnish Master to ensure on-cache flush one request (at most) per web tier +- [ ] A Varnish cluster can scale to the traffic of a site +- [ ] Tune the instance size based on the number of cache pages needed +- [ ] On a high-traffic site, use a Varnish Master to ensure on-cache flush one request (at most) per web tier ## Web -- Enable scale of nodes for traffic and redundancy -- One node is master and runs cron -- Alternatively, use a dedicated Admin and worker nodes +- [ ] Enable scale of nodes for traffic and redundancy +- [ ] One node is master and runs cron +- [ ] Alternatively, use a dedicated Admin and worker nodes ## Cache -- Consider implementing a separate Redis instance for sessions -- You can have a Redis instance per cache -- Size your instance to contain the largest expected cache size +- [ ] Consider implementing a separate Redis instance for sessions +- [ ] You can have a Redis instance per cache +- [ ] Size your instance to contain the largest expected cache size ## Database and queues -- High-traffic sites can tune DB performance with slave DBs and split DBs for orders/carts (in Adobe Commerce) -- Consider using a slave DB to enable quick recovery and for data backups -- Low-traffic sites can store images in the DB +- [ ] High-traffic sites can tune DB performance with slave DBs and split DBs for orders/carts (in Adobe Commerce) +- [ ] Consider using a slave DB to enable quick recovery and for data backups +- [ ] Low-traffic sites can store images in the DB ## Search -- Tune the number of instances based on search traffic +- [ ] Tune the number of instances based on search traffic ## Storage -- Consider using GFS or GlusterFS for pub/media storage -- Alternatively, use DB storage for low-traffic sites +- [ ] Consider using GFS or GlusterFS for pub/media storage +- [ ] Alternatively, use DB storage for low-traffic sites