---
title: "Discussion on \"Event Sourcing vs CRUD\" | Hashnode"
description: "Discussion on \"Event Sourcing vs CRUD\". On January 31, 2017, an engineer at GitLab ran a command meant to clear a stalled replication database. He ran it on the wrong terminal, against the primary production database. In seconds, around 300"
url: "https://hashnode.com/posts/event-sourcing-vs-crud/6a5c6fd75a6becd3b6ac7fea"
---

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

Discussion

# [Event Sourcing vs CRUD](https://backend-bytes.hashnode.dev/event-sourcing-vs-crud?utm_source=hashnode&utm_medium=feed)

On January 31, 2017, an engineer at GitLab ran a command meant to clear a stalled replication database. He ran it on the wrong terminal, against the primary production database. In seconds, around 300

Jul 19 · 5 min read · backend-bytes.hashnode.dev  
Read the article

-   [#event-sourcing](https://hashnode.com/tag/event-sourcing)
-   [#system-design](https://hashnode.com/tag/system-design)
-   [#backend-development](https://hashnode.com/tag/backend-development)
-   [#crud](https://hashnode.com/tag/crud)
-   [#software-engineering](https://hashnode.com/tag/software-engineering)

## Written by

[Devesh Parmar](https://hashnode.com/@deveshparmar)

@deveshparmar · Ahmedabad, Gujarat

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

SDE @ Ei

Software Development Engineer ~ System Design, AI, Finance, Tech

## Responses

Markdown supported · ⌘↵ to post

No responses yet.