From 0d30bf29502c560ca5b0a469af138b47d763afd8 Mon Sep 17 00:00:00 2001 From: dd di cesare Date: Fri, 9 Feb 2024 08:10:08 +0100 Subject: [PATCH] [rfc] Rationale and alternatives --- rfcs/0000-limitador-multithread-inmemory.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rfcs/0000-limitador-multithread-inmemory.md b/rfcs/0000-limitador-multithread-inmemory.md index de9fe848..90e8aa4e 100644 --- a/rfcs/0000-limitador-multithread-inmemory.md +++ b/rfcs/0000-limitador-multithread-inmemory.md @@ -204,9 +204,9 @@ that the service operates correctly and efficiently. # Rationale and alternatives [rationale-and-alternatives]: #rationale-and-alternatives -- Why is this design the best in the space of possible designs? -- What other designs have been considered and what is the rationale for not choosing them? -- What is the impact of not doing this? +- **Single-threaded**: We could choose to keep the current single-threaded implementation of Limitador, which would + maintain the simplicity and predictability of the service, but would limit its ability to handle concurrent requests + and process requests at a higher throughput. # Prior art [prior-art]: #prior-art