---
title: "Discussion on \"Automerge vs GenosDB: The Price of Keeping Every Version\" | Hashnode"
description: "Discussion on \"Automerge vs GenosDB: The Price of Keeping Every Version\". Automerge keeps the full history of every change — a real capability with a real invoice: memory, a 45 MB WebAssembly package, and a sync layer that has never left alpha."
url: "https://hashnode.com/posts/automerge/6aa8121f24584c40f7072bbd"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Automerge vs GenosDB: The Price of Keeping Every Version](https://genosdb.com/automerge?utm_source=hashnode&utm_medium=feed)

Automerge keeps the full history of every change — a real capability with a real invoice: memory, a 45 MB WebAssembly package, and a sync layer that has never left alpha.

Sep 14 · 10 min read · genosdb.com  
Read the article

-   [#crdt](https://hashnode.com/tag/crdt)
-   [#peer-to-peer](https://hashnode.com/tag/peer-to-peer)
-   [#javascript](https://hashnode.com/tag/javascript)
-   [#databases](https://hashnode.com/tag/databases)
-   [#webassembly](https://hashnode.com/tag/webassembly)

## Written by

[Esteban Fuster Pozzi (estebanrfp)](https://hashnode.com/@estebanrfp)

@estebanrfp · Valencia, España

  
[View profile](https://hashnode.com/@estebanrfp)

Full Stack Developer - dWEB R&D

Full Stack Developer - dWEB R&amp;D

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
