2b. What it is not for

Mobile applications. Bagri client module is about 20M, but this is, probably, too much for mobile app. When the standard entity-relationship RDBMS model is enough, the data model is quite static and data comes to the system in some predefined format with no meta-data tags and subsequent data processing is relatively simple (can be done by standard SQL queries) then there is no need for Bagri. When there are RAM limitations on the server side. Bagri extracts and keeps processed documents in efficient memory structures, separating metadata from the data itself. As a solution, based on a distributed cache technology, it provides the best data access speed by cost of memory utilization. See the sample memory allocation in the prerequisites section. So, if you have a relatively big number of documents, but small amount of RAM then do not use Bagri.