From f0937689d584b0da0f34f26f941b6fbeb41a835e Mon Sep 17 00:00:00 2001 From: Alexis VIALARET Date: Thu, 4 Jan 2024 17:55:28 +0100 Subject: [PATCH] del: archi from readme --- README.md | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/README.md b/README.md index 521de5f..fb78139 100644 --- a/README.md +++ b/README.md @@ -41,20 +41,6 @@ streamlit run frontend/app.py You should than be able to login and chat to the bot: ![](docs/login_and_chat.gif) - -## Architecture - -### The `frontend`, the `backend`, and the `database` - -The whole goal of this repo is to decouple the "computing and LLM querying" part from the "rendering a user interface" part. We do this with a typical 3-tier architecture. - -![](docs/3t_architecture.png) - -- The [frontend](frontend) is the end user facing part. It reches out to the backend **ONLY** through the REST API. We provide a frontend demo here for convenience, but ultimately it could live in a completely different repo, and be written in a completely different language. -- The [backend](backend) provides a REST API to abstract RAG functionalities. It handles calls to LLMs, tracks conversations and users, handles the state management using a db, and much more. To get the gist of the backend, look at the of the API: http://0.0.0.0:8000/docs -- The [database](database) is only accessed by the backend and persists the state of the RAG application. [Explore the data model here.](https://dbdiagram.io/d/RAGAAS-63dbdcc6296d97641d7e07c8) - - ## Documentation To deep dive into under the hood, take a look at the documentation: