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
@@ -21,62 +27,84 @@ Schema-less persistence for Smalltalk with support for multiple backends.
21
27
- Composable.
22
28
- JSON friendly.
23
29
- No need to create accessors and mutators.
24
-
- Multiple backends to chose from.
30
+
- Multiple backends to choose from.
25
31
- Enables smooth data migration/interoperation among backends.
26
-
- Via Redis PUB/SUB, scalable observer-pattern functionality across images.
32
+
-~~Via Redis PUB/SUB, scalable observer-pattern functionality across images.~~ In the roadmap.
33
+
34
+
## Description
35
+
36
+
Mapless is a schema-less persistence framework supporting multiple backends and offering a user-friendly API. For instance, querying Mapless objects involves a common family of methods, and there's no need to declare accessors and mutators. See [examples below](#examples).
37
+
38
+
Designed to be schema-less, Mapless eliminates the need for schema maintenance and avoids any Object-Relational Mapping requirements.
39
+
40
+
Mapless achieves a balance of maximum data survivability and robust architectural flexibility without imposing a heavy burden in terms of adoption and maintenance.
27
41
28
42
## Ambition
29
43
30
-
Mapless gives you performant state plasticity and high availability in a scale that goes beyond one Smalltalk image and without backend vendor locking nor object-mapping impedance mismatch.
44
+
To deliver a high-performance solution that preserves arbitrary application state (data) with a focus on flexibility, availability, and capacity. It aims to strategically aid in scaling without causing backend vendor lock-in, across various persistence backends, and by neutralizing the costs associated with object-mapping impedance mismatch.
Copy file name to clipboardExpand all lines: changelog.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,9 @@
1
+
Jan 25, 2024
2
+
===================================
3
+
- Updating `master` branch to keep up with the latests useful upgrades.
4
+
- Adding badges to the README.md for constant monitoring of CI, unit tests, regression detection capacity and supported Pharo versions.
5
+
- Adds CI via GitHub actions.
6
+
1
7
May 22, 2023
2
8
===================================
3
9
- Improved `MongoAPI` by adding `initializeMongoUrl` and a lazy accessor using it and `Array` instead of `Set` so comparing it on the fly from `getIdleReadOnlyClient` is significantly faster now.
0 commit comments