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
Copy file name to clipboardExpand all lines: README.md
+10-4Lines changed: 10 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,15 @@ No new features will be added. Critical security fixes may be considered on a be
10
10
We are the original authors of Mongock. Over the last 1–2 years we’ve been heads‑down building **[Flamingock](https://github.com/flamingock/flamingock-project)** — a platform inspired by what worked in Mongock, but with a much broader scope: **auditable, deterministic evolution across your whole system**. (A managed cloud offering is also in the works.)
11
11
12
12
- Covers everything Mongock did for MongoDB/NoSQL migrations **and much more**
13
-
- Orchestrates changes across databases, message queues, APIs, infrastructure, feature flags, etc.
13
+
- Orchestrates changes across message queues, APIs, databases, feature flags, etc.
14
14
- Built with auditability, determinism, and governance at its core
15
15
16
+
### More highlights
17
+
- Flexible/no‑code templates for defining changes
18
+
- Native GraalVM support
19
+
- Advanced multi-stage workflow
20
+
- …and more in the docs → [Features overview](https://docs.flamingock.io/docs/1.0.0/overview/key-features)
21
+
16
22
> Same creators. Broader scope. Better foundations.
@@ -21,8 +27,8 @@ We are the original authors of Mongock. Over the last 1–2 years we’ve been h
21
27
22
28
## Why the change?
23
29
24
-
Mongock focused on database migrations (mainly MongoDB and other NoSQL stores).
25
-
But real-world evolution goes beyond schemas: it touches contracts, queues, configs, infra, and compliance.
30
+
Mongock focused and helped teams evolve NoSQL databases with confidence.
31
+
But we realized that real-world evolution goes beyond databases: it touches contracts, queues, configs, compliance, etc.
26
32
**Flamingock is the natural evolution** to cover that larger problem space — not a direct continuation, but a new platform that also does what Mongock did.
27
33
28
34
---
@@ -31,7 +37,7 @@ But real-world evolution goes beyond schemas: it touches contracts, queues, conf
31
37
32
38
- Your current versions will keep working as-is.
33
39
- We strongly recommend evaluating Flamingock for new projects or when planning significant changes.
34
-
-Migration help: see **[How to move from Mongock to Flamingock](https://docs.flamingock.io)**.
40
+
-Upgrade help: see **[How to move from Mongock to Flamingock](https://docs.flamingock.io/docs/1.0.0/resources/upgrade-from-mongock)**.
0 commit comments