You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**In‑memory SQLAlchemy 2.0 dialect for blazing‑fast prototyping**
8
+
**In‑memory SQLAlchemy 2.0 dialect for blazing‑fast prototyping**
9
9
10
-
A pure‑Python, zero‑configuration SQLAlchemy 2.0 dialect that lives entirely in RAM.
11
-
Ideal for rapid prototyping, backtesting, and demos-no external database required.
10
+
A pure‑Python SQLAlchemy 2.0 dialect that runs entirely in RAM.
11
+
It avoids typical database I/O and ORM overhead while maintaining full compatibility with the SQLAlchemy 2.0 Core and ORM APIs.
12
+
Ideal for rapid prototyping, backtesting engines, simulations.
12
13
13
14
## Why ?
14
15
15
-
This project was inspired by the idea of creating a fast, introspectable, no-dependency backend for SQLAlchemy. Useful for prototyping, education, and testing ORM logic without spinning up a real database engine.
16
+
This project was inspired by the idea of building a **fast, introspectable, no-dependency backend** for SQLAlchemy.
16
17
17
-
It's also perfect for apps that need a fast, in-memory store compatible with SQLAlchemy, such as backtesting engines, simulators, or tools where you don't want to maintain a separate memory layer alongside your database models.
18
+
It is useful for:
19
+
20
+
- Prototyping new applications
21
+
22
+
- Educational purposes
23
+
24
+
- Testing ORM logic without spinning up a real database engine
25
+
26
+
Unlike traditional in-memory solutions like SQLite, `sqlalchemy-memory` fully avoids serialization, connection pooling, and driver overhead, leading to much faster in-memory performance while keeping the familiar SQLAlchemy API.
27
+
28
+
It is also perfect for **applications that need a lightweight, high-performance store** compatible with SQLAlchemy, such as backtesting engines, simulators, or other tools where you don't want to maintain a separate in-memory layer alongside your database models.
0 commit comments