# Architecture

CellBase has been implemented in a very modular way providing a three layer architecture, enabling different access levels and use cases of the system:

1. MongoDB Databases in current implementation. An independent MongoDB database is created for each species and assembly. Collection

   schemas and indexes were designed to ensure an efficient response to the main expected queries (See MongoDB implementation for detailed specification of current mongo schema)
2. A Java abstraction layer that deals with the peculiarities of the underlying database system and provides an API to access the data (DB

   Adaptors). Advanced users may directly use this API to avoid network access and web services overload thus improving the performance of their implementations. Moreover, any advanced user wanting to use any other database system will just have to implement this API plugin for the desired database system. A cache system based on a Redis server is currently under development.
3. A set of REST Web Services and gRPC API which provide an efficient high level interface to the data regardless of the programming language. Most frequent access will be through this top layer. Thus, the Web Services API can be queried either by provided clients in Python, R, Java and JavaScript, the Java CLI or by own user-developed methods that implement calls to the Web Services by building appropriate urls. Comprehensive RESTful API specification is provided by Swagger: <http://bioinfo.hpc.cam.ac.uk/cellbase/webservices/> (Note: Python client is available in current develop branch, future 4.5.0 release. A first approach to the R client is also available and under development).

![](/files/-MHQO6UYRCTwaCFCJEB-)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.cellbase.opencb.org/architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.