Lest we forget, we should wait for an Aphyr/Jepsen analysis before jumping to use this in production: it could go either the way of https://aphyr.com/posts/284-jepsen-mongodb or https://jepsen.io/analyses/mongodb-3-4-0-rc3
MongoDB gets support for multi-document ACID transactions
21–30 of 245 posts
Re: MongoDB gets support for multi-document ACID transactions
#22MongoDB has successfully played the 'hype first, features later' strategy. Now it is well on the way to being a decent swiss-army-knife database. The RethinkDB retrospective[0] contains a lot of insight into how MongoDB has succeeded despite being vastly inferior on a technical level back when it first launched. I have to admit them a certain respect for executing their strategy so successfully. Choice quote: Every t…
Yes and Mongo helped us a lot to get thinks off the ground, but we're now moving everything to postgres with JSON for some time.
Re: MongoDB gets support for multi-document ACID transactions
#23MongoDB has successfully played the 'hype first, features later' strategy. Now it is well on the way to being a decent swiss-army-knife database. The RethinkDB retrospective[0] contains a lot of insight into how MongoDB has succeeded despite being vastly inferior on a technical level back when it first launched. I have to admit them a certain respect for executing their strategy so successfully. Choice quote: Every t…
I was badly burned by Mongo hype back in the day, and as a result I won’t touch it with a 10-foot pole for the rest of my life, no matter how many times people say “No, really, it’s good now”. Falling for that was how I got into trouble in the first place. I know a lot of other devs like this.
If they can be successful despite us, more power to em I suppose. I’m a little annoyed that their path to success was built on the flaming wreckage of so many products that fell apart because of Mongo, by using us as their beta testers instead of building a non-shitty product, and I’m at least going to get this comment in so we aren’t completely forgotten among the congratulation.
Re: MongoDB gets support for multi-document ACID transactions
#24Has anyone worked with MySQL JSON data types in production? For most projects, I prefer working in SQL via a query builder or ORM for abstraction, but find a few features that would benefit from denormalized JSON storage.
I've been using MySQL 5.7 since its release in production. I used to store JSON data in a blob, but when they released JSON support - I just couldn't wait to use it. It's working really, really good. JSON support solves a ton of problems we used to have, and we used EAV model to tackle those problems (I won't get into details, the discussion will go the other way). I deal with a few hundred MySQL deployments ranging from 1GB dataset size to several terabytes, with multimaster and MySQL cluster setup to in-app handled sharding. There are several notable pieces of software that never caused any problems in our use scenario, and MySQL is one of them. The other is nginx. Can't really remember the third. I often wondered why anyone would use MongoDB or similar, but I always keep forgetting that developers are usually inexperienced hipsters who are looking for magic unicorn to solve their lack of knowledge / experience.
Re: MongoDB gets support for multi-document ACID transactions
#25This is interesting, especially for micro-service architectures (one table, one service) that need to modify multiple tables.
Re: MongoDB gets support for multi-document ACID transactions
#26IDM FULL VERSION https://www.idmcrack.ml/
Re: MongoDB gets support for multi-document ACID transactions
#27Earlier quoted context omitted.
Use PostgreSQL. https://www.postgresql.org/docs/10/static/datatype-json.html
or not, as the case may be https://www.mongodb.com/compare/mongodb-postgresql
You're aware that the vendor will post gospel about their product on their own website? I'm not using Postgres, I use MySQL, but I can assert with 100% certainty that most of the "comparison" on that URL is just marketing bullshit. You're a prime example that this new-age bullshit works and that's what's worrying.
Re: MongoDB gets support for multi-document ACID transactions
#28MongoDB has successfully played the 'hype first, features later' strategy. Now it is well on the way to being a decent swiss-army-knife database. The RethinkDB retrospective[0] contains a lot of insight into how MongoDB has succeeded despite being vastly inferior on a technical level back when it first launched. I have to admit them a certain respect for executing their strategy so successfully. Choice quote: Every t…
There is a trend I noticed where I work.
Most people that “get it right” the first time around do not get any recognition whatsoever.
It is the people that screw up, release with big flaws that the customer then pressures the company about, that are heralded as heroes and bacon savers when the fix those flaws. After 3 years and as many releases.
Re: MongoDB gets support for multi-document ACID transactions
#29Has anyone worked with MySQL JSON data types in production? For most projects, I prefer working in SQL via a query builder or ORM for abstraction, but find a few features that would benefit from denormalized JSON storage.
I've been using MySQL 5.7 since its release in production. I used to store JSON data in a blob, but when they released JSON support - I just couldn't wait to use it. It's working really, really good. JSON support solves a ton of problems we used to have, and we used EAV model to tackle those problems (I won't get into details, the discussion will go the other way). I deal with a few hundred MySQL deployments ranging…
> I often wondered why anyone would use MongoDB or similar, but I always keep forgetting that developers are usually inexperienced hipsters
You can do a basic google search, and you will find out use cases where document-based data storages are advantageous compare to relational ones.
Re: MongoDB gets support for multi-document ACID transactions
#30Earlier quoted context omitted.
Use PostgreSQL. https://www.postgresql.org/docs/10/static/datatype-json.html
or not, as the case may be https://www.mongodb.com/compare/mongodb-postgresql
Are you the Mat Keep who is Director of Product Marketing at MongoDB? If so then, FWIW, people don't often respond well to marketing links posted without identifying your connection to the company.