From b533c5c56d20312124107cf5dd7f1b7132c0d3e8 Mon Sep 17 00:00:00 2001 From: "Mohammad A. Ali" Date: Sun, 19 May 2024 21:59:00 +0200 Subject: [PATCH] Update README.md --- README.md | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/README.md b/README.md index 76e6a7f..cd3af9d 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,6 @@ ![litestack](https://github.com/oldmoe/litestack/blob/master/assets/litestack_logo_teal_large.png?raw=true) Gem Version -CI Status RubyGems Downloads All your data infrastructure, in a gem! @@ -12,16 +11,6 @@ Compared to conventional approaches that require separate servers and databases, You can read more about why litestack can be a good choice for your next web application **[here](WHYLITESTACK.md)**, you might also be interested in litestack **[benchmarks](BENCHMARKS.md)**. -litestack provides integration with popular libraries, including: - -- Rack -- Sequel -- Rails -- ActiveRecord -- ActiveSupport::Cache -- ActiveJob -- ActionCable - With litestack you only need to add a single gem to your app which would replace a host of other gems and services, for example, a typical Rails app using litestack will no longer need the following services: - Database Server (e.g. PostgreSQL, MySQL) @@ -31,6 +20,7 @@ With litestack you only need to add a single gem to your app which would replace - Fulltext Search Server (e.g. Elasticsearch, Meilisearch) To make it even more efficient, litestack will detect the presence of Fiber based IO frameworks like Async (e.g. when you use the Falcon web server) or Polyphony. It will then switch its background workers for caches and queues to fibers (using the semantics of the existing framework). This is done transparently and will generally lead to lower CPU and memory utilization. +![litestack](https://github.com/oldmoe/litestack/blob/master/assets/litestack_advantage.png?raw=true) ## Installation