jd_mongodb

You knowledge of MongoDB is a little out of date.

MongoDB supports SQL queries. Tableau has an MongoDB connector. You can connect MongoDB to Excel via our DataAPI and of course our Cloud platform provides embeddable charts.

Only the DataAPI is a relatively recent addition. The rest are very mature features.

Comparing any modern database (i.e. developed after 1980) with IMS is like comparing a flint knife with a Barrett .50 calibre.

We would love to help promote this? Ping me Joe dot Drumgoole at mongodb.com as we can get you some time on our podcast.

See also https://www.mongodb.com/developer/products/atlas/atlas-data-...

See also https://www.youtube.com/watch?v=9MFv8J7Smws

See https://cloud.google.com/blog/products/data-analytics/mongod...

MongoDB provides MongoDB Atlas, our own managed service. which is supported on every cloud (AWS, Azure, GCP).

We have recognised this problem and to that end we have produced a Stable API standard https://www.mongodb.com/docs/manual/reference/stable-api/

I realise this doesn't help you with historical API changes.

If you look for help in the MongoDB community and tag me (Joe.Drumgoole@mongodb.com) I will make sure you get help migrating your app.

https://www.mongodb.com/community/forums/

MongoDB has an SQL interface these days if you need it

https://www.mongodb.com/atlas/sql

I am not disputing the bill, just curious how he got there. He doesn't say in his post.

I did manage to approach his costs by running a sharded cluster with our largest configuration (M600 nodes with 640GB RAM. 4TB storage and 3.8m IOPS).

That is priced quite clearly on the bottom page at 102.49 USD an hour.

MongoDB actually doesn't store JSON. It stores a binary encoding of JSON called BSON (Binary JSON) which encodes type and size information.

This means we can encode objects in your program directly into objects in the database. It also means we can natively encode documents, sub-documents, arrays, geo-spatial coordinates, floats, ints and decimals. This is a primary function of the driver.

This also allows us to efficiently index these fields, even sub-documents and arrays.

All MongoDB collections are compressed on disk by default.

(I work for MongoDB)

Every field in a MongoDB document (we encoded documents in BSON at the driver level) is typed and you can apply a schema to any collection if you choose to do so.

It's almost as if MongoDB didn't create the JSON API that practically everyone has adopted.

Do you have a reference to that article?

Can share some more details? Site looks fine now. A screen shot perhaps. You can always ping the @mongodb twitter when you see issues like this.

I can see the source of confusion. Apologies. I mentioned ACID transactions were released in 4.0 but did not explicitly mention when the problems arose which of course was in 4.2 which was actually released a year later. The version numbers are clearly referenced in the Jepsen article.

Also read the addendum from the same report:

1 Updates 2020-05-26: MongoDB identified a bug in the transaction retry mechanism which they believe was responsible for the anomalies observed in this report; a patch is scheduled for 4.2.8.

You must not have looked at MongoDB. We have been delivering fully consistent ACID transactions since 4.0 which shipped several years. Yes, Jepsen did find some issues with the initial release of ACID transactions and yes, we fixed those problems pretty rapidly.

I don't think I mentioned role model. We most definitely don't model ourselves on IBM. I was just pointing out their longevity which is impressive to me.

Oracle's doom is a tricky one to predict, they have been around for a long time. Can they survive Larry Ellison's retirement? Who can tell?

But IBM? You are having a laugh. IBM was there at the start of the computer industry and they have survived every single generation of change since, getting stronger each time.

Saying IBM has faded in relevance is absolutely farcical.

If you want to ping me an email at Joe.Drumgoole@mongodb.com I can get that fixed pretty quickly.

Try typing "mongodb customers" into Google.

Here is a few I know are public references:

MetLife, Epic Games, Bosch, Inland Revenue (UK), Department of Work and pensions (UK) Barclays, HSBC, Boots, Forbes, Toyota, Sanoma, Intuit, Verizon.

Steve left many years before MongoDB Atlas launched

You seem to think MongoDB is eventually consistent. MongoDB is designed as strongly consistent database. You can choose to query a secondary and that will be eventually consistent but that is not the default behaviour.

You have been able to do SQL queries in MongoDB since 2018. Just this month we launched AtlasSQL, a new SQL query interface purpose built for MongoDB Atlas.

That is a pretty old paper if they made the switch before MongoDB 4.0 was introduced. 4.0 was released in 2018. One from the archives.

thanks for the ticket Matt.

Of course if you don't like the id's that MongoDB generates by default you can always the supply your own. The only constraint on the _id field is that it be unique as we automatically apply a unique index. Effectively if you have a unique key for your data you should use _id for it as it saves you an index. (We always index _id).

(I work for MongoDB).

When you booted the Mongo client library what did you use in it's place? Were you connecting to a cluster or a single node? Lightweight clients are always interesting because of the trade offs they make.