Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Data Corruption: It's the Code, Not the Database

DZone's Guide to

Data Corruption: It's the Code, Not the Database

· Database Zone ·
Free Resource

Discover Tarantool's unique features which include powerful stored procedures, SQL support, smart cache, and the speed of 1 million ACID transactions on a single CPU core!

I am increasingly convinced that those who blame MongoDB for any kind of data corruption are waving hands out of desperation. Every single time I had an issue with data I ended up finding code that I’ve written or code that was written in a library that I used. The hardest bugs involve some kind of concurrent operation, including one I’ve described in a new post on the Artsy Engineering blog: Data Corruption and Concurrent Updates to Embedded Objects w/ MongoDB. Read it, especially if you are using an ODM to manipulate embedded objects.

I also want to point out two magical lines of code that I use all the time.

    Moped.logger = Logger.new($stdout)
    Moped.logger.level = Logger::DEBUG

Knowing what Mongoid is doing is half the battle.

Discover Tarantool's unique features such as powerful stored procedures, SQL support, smart cache, and the speed of 1 million ACID transactions on a single CPU.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}