Does anyone here have an idea of how popular mongoDB is?
-
It's one of the most popular databases and the most popular NoSQL database. Source: DB-Engines Ranking - popularity ranking of database management systems[^] No idea why Oracle is at #1 though, must be some kind of Stockholm syndrome thing :~ Anyway, I've used MongoDB in the past and it's very easy to just write some code and store it in the database. Except that when you add a property you always need to think about whether that property is backwards compatible. You have to do that with SQL too, of course, but there you are more forced to think about it. It's VERY easy to just add a new property of type int, but when a MongoDB document doesn't have that property you're going to have a runtime mapping exception so you'll have to make it int? instead, etc. Also, forget normalization. If you have a highly normalized data structure, MongoDB is going to make life harder. So really think about what data you can store with redundancy and what data you can't. Also, I found querying a MongoDB a lot harder, but that's probably only because I'm not used to the syntax :o I'm not used to seeing you use popular technology by the way, unless you're going to use this for your LALR X-PARSE B-TREE REGEX EXPRESSION COMPILER +5 :laugh:
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
I've been out of the professional dev field for some time but I've run across mongoDB backed REST based repositories like TMDB's. They're really easy to tightly integrate with a JSON based caching entity framework. What I'm really asking is if mongoDB is the "go to" for REST based JSON repositories or is there a more popular offering out there these days?
Real programmers use butterflies
MongoDB - where GUIDs are displayed in the wrong order just to punish you. 2/5 would not use again.
-
[CouchDB](https://couchdb.apache.org/) is another alternative, but MongoDB is the one I hear mentioned most often. Having said that, a lot of those mentions are on infosec news, when someone's left their MongoDB store up, unprotected, on Amazon S3 and the data in it has been compromised... That's not MongoDB's fault, of course
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
Stuart Dootson wrote:
That's not MongoDB's fault, of course
Well, in part. Their default setting is (was?) unprotected and open for all to see :~ That's a very dubious default and one that many people failed to change!
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
Stuart Dootson wrote:
That's not MongoDB's fault, of course
Well, in part. Their default setting is (was?) unprotected and open for all to see :~ That's a very dubious default and one that many people failed to change!
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Sander Rossel wrote:
Their default setting is (was?) unprotected and open for all to see :~
The reports I've heard were implying more that the S3 permissions had been defaulted, so anyone could access (and download) the datastore rather than accessing the associated MongoDB server.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
-
Sander Rossel wrote:
Their default setting is (was?) unprotected and open for all to see :~
The reports I've heard were implying more that the S3 permissions had been defaulted, so anyone could access (and download) the datastore rather than accessing the associated MongoDB server.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
I may be thinking of another incident where researchers just tried the default MongoDB port on thousands of servers and found that for many of those servers the port was open and the database was exposed.
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
It's one of the most popular databases and the most popular NoSQL database. Source: DB-Engines Ranking - popularity ranking of database management systems[^] No idea why Oracle is at #1 though, must be some kind of Stockholm syndrome thing :~ Anyway, I've used MongoDB in the past and it's very easy to just write some code and store it in the database. Except that when you add a property you always need to think about whether that property is backwards compatible. You have to do that with SQL too, of course, but there you are more forced to think about it. It's VERY easy to just add a new property of type int, but when a MongoDB document doesn't have that property you're going to have a runtime mapping exception so you'll have to make it int? instead, etc. Also, forget normalization. If you have a highly normalized data structure, MongoDB is going to make life harder. So really think about what data you can store with redundancy and what data you can't. Also, I found querying a MongoDB a lot harder, but that's probably only because I'm not used to the syntax :o I'm not used to seeing you use popular technology by the way, unless you're going to use this for your LALR X-PARSE B-TREE REGEX EXPRESSION COMPILER +5 :laugh:
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
This is a nice write-up and has some valuable points. I would also add that yes, MongoDB is quite popular based on the fact that it had an IPO and you can buy stock in the company: MongoDB current stock price[^] That may sound a bit ridiculous but I mean it does show a bit of consumer and investor confidence and that the company itself seems to be solid.
-
MongoDB - where GUIDs are displayed in the wrong order just to punish you. 2/5 would not use again.
I wasn't asking for a review
Real programmers use butterflies
-
I may be thinking of another incident where researchers just tried the default MongoDB port on thousands of servers and found that for many of those servers the port was open and the database was exposed.
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
No, you're quite right - [that's another attack vector](https://www.mongodb.com/blog/post/how-to-avoid-a-malicious-attack-that-ransoms-your-data)...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
-
I've been out of the professional dev field for some time but I've run across mongoDB backed REST based repositories like TMDB's. They're really easy to tightly integrate with a JSON based caching entity framework. What I'm really asking is if mongoDB is the "go to" for REST based JSON repositories or is there a more popular offering out there these days?
Real programmers use butterflies
Apparently it is the wave of the future
Member 12321939
in my project i am using MongoDB in there sample they use MySQL which is deprecated
[Quick Answers =>How to get fingerprint with u.are.u 4500 using PHP](https://www.codeproject.com/Questions/5267246/How-to-get-fingerprint-with-u-are-u-4500-using-PHP)
Director of Transmogrification Services Shinobi of Query Language Master of Yoda Conditional
-
It's one of the most popular databases and the most popular NoSQL database. Source: DB-Engines Ranking - popularity ranking of database management systems[^] No idea why Oracle is at #1 though, must be some kind of Stockholm syndrome thing :~ Anyway, I've used MongoDB in the past and it's very easy to just write some code and store it in the database. Except that when you add a property you always need to think about whether that property is backwards compatible. You have to do that with SQL too, of course, but there you are more forced to think about it. It's VERY easy to just add a new property of type int, but when a MongoDB document doesn't have that property you're going to have a runtime mapping exception so you'll have to make it int? instead, etc. Also, forget normalization. If you have a highly normalized data structure, MongoDB is going to make life harder. So really think about what data you can store with redundancy and what data you can't. Also, I found querying a MongoDB a lot harder, but that's probably only because I'm not used to the syntax :o I'm not used to seeing you use popular technology by the way, unless you're going to use this for your LALR X-PARSE B-TREE REGEX EXPRESSION COMPILER +5 :laugh:
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Sander Rossel wrote:
you're going to have a runtime mapping exception
Only if you're using a strongly typed language. Javascript (or even TypeScript) with NodeJS does not have that problem, although I do agree you still need to think about it.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
-
Sander Rossel wrote:
you're going to have a runtime mapping exception
Only if you're using a strongly typed language. Javascript (or even TypeScript) with NodeJS does not have that problem, although I do agree you still need to think about it.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson ---- Our heads are round so our thoughts can change direction - Francis Picabia
Yeah, it's not a problem if you use NodeJS, but I'm assuming honey is using C# :) Of course you still can't just add number2 after some weeks of production (and always set it for new records) and then somewhere do number1 + number2, assuming they both have a value. Even if number1 always has a value, number2 only gets a value at some point in time, unless you do a collection update like you'd do in a SQL database. When I worked with MongoDB we used to do that because updating the entire collection is easier than updating the entire software :laugh: For the record, I didn't think we needed MongoDB, SQL would've been fine, especially when you want schema integrity anyway, but it was the decision of our architect. At least it gave me a chance to work with MongoDB in a production environment.
Best, Sander sanderrossel.com Migrating Applications to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
