Web Application VS Windows Application
-
-
@IT-ADMIN said:
i'm just reading about MangoDB
http://www.tutorialspoint.com/mongodb/mongodb_overview.htmdo you know a good documentation about this ?? or the above link is good ??
We are recording this conversation on MongoDB
If you search for MongoDB in titles in MangoLassi, you will find that I wrote up an install guide for it last week MongoDB's own website is pretty decent for getting you started. However, you don't need to learn the database to use it. Many frameworks, like Meteor, use it by default and everything that you need to interact with it is built in. So you can focus on programming, instead of on designing databases.
-
One thing that is interesting about MongoDB is that it is built with an JavaScript interface and its native language is JSON.
-
sometimes i say how people like you have time to even discuss in this forum, he could be hired by big companies like google or apple, and not wasting his time with people like me
-
@IT-ADMIN said:
sometimes i say how people like you have time to even discuss in this forum, he could be hired by big companies like google or apple, and not wasting his time with people like me
Google has an NDA on interview processes, they can't even get me to talk to them. Apple has tried, nice people, but they don't pay enough for the kind of work and location (they pushed for me in Cupertino, they wouldn't let me work from their Austin office, so their pay rate just wasn't good enough.)
-
@scottalanmiller said:
@IT-ADMIN said:
i'm just reading about MangoDB
http://www.tutorialspoint.com/mongodb/mongodb_overview.htmdo you know a good documentation about this ?? or the above link is good ??
We are recording this conversation on MongoDB
If you search for MongoDB in titles in MangoLassi, you will find that I wrote up an install guide for it last week MongoDB's own website is pretty decent for getting you started. However, you don't need to learn the database to use it. Many frameworks, like Meteor, use it by default and everything that you need to interact with it is built in. So you can focus on programming, instead of on designing databases.
In the event that you do try Meteor.js and your colleague doesn't like it, there is a PHP library for MongoDB as well.
-
Ok, is it possible to use MongoDB if we have a relation many to many in our data model ?? i know it is possible but is it that simple as RDBMS ???
-
@IT-ADMIN said:
Ok, is it possible to use MongoDB if we have a relation many to many in our data model ?? i know it is possible but is it that simple as RDBMS ???
This question doesn't even make sense.
You not be using your model, of course. The model that you have made exists solely to service a system you shouldn't be using. Just skip it.No, it is far SIMPLER. Everything you have done already is unnecessary. not that it is all bad, it is good to know the data. But you are overthinking this. NoSQL makes this far easier in your case (and nearly all cases.) You are mired in the complexities of relational databases, you need to think more simply and more easily.
-
@dafyre said:
@scottalanmiller said:
@IT-ADMIN said:
i'm just reading about MangoDB
http://www.tutorialspoint.com/mongodb/mongodb_overview.htmdo you know a good documentation about this ?? or the above link is good ??
We are recording this conversation on MongoDB
If you search for MongoDB in titles in MangoLassi, you will find that I wrote up an install guide for it last week MongoDB's own website is pretty decent for getting you started. However, you don't need to learn the database to use it. Many frameworks, like Meteor, use it by default and everything that you need to interact with it is built in. So you can focus on programming, instead of on designing databases.
In the event that you do try Meteor.js and your colleague doesn't like it, there is a PHP library for MongoDB as well.
But you will likely make everything harder. It's hard to get easier than Meteor.
-
is mongoDB opensource, right??
-
in my above data model diagram, where i have many to many relationships between entities, what is the best approach: references or embedded documents ??
-
-
dear Scott please can you tell me what are the right steps to follow when working with document DB ?? i mean are there any models to follow in document DB similar to Merise or UML in relational DB ??
-
@IT-ADMIN said:
dear Scott please can you tell me what are the right steps to follow when working with document DB ?? i mean are there any models to follow in document DB similar to Merise or UML in relational DB ??
No, I don't believe any modeling tools like that have been created yet. Although the need for them mostly does not exist.
-
Try this, take Word and try making a sample "document" of sample data for one or two users. That should, mostly, guide you as to what the MongoDB document will look like.
Do it something like this...
First Name: John
Last Name: Doe
SSID: 123.45.678
Cell Phone: (132) 465-7896Something like that.
-
wow, how it can be arbitrary like this, no rules, no models to follow,
strange
-
@IT-ADMIN said:
wow, how it can be arbitrary like this, no rules, no models to follow,
strangeThere are rules, they are just more lax and flexible. Maybe a better question would be... what were all of those rules for?
-
ah i see, so there are rules, can you please give me any guide how to start a project using document DB from A to Z, because really i'm lost in this stage, document DB is new for me and i do not know where i should start,
you can imagine someone hear something for the first time and he is ignorant of the steps he should follow -
before with relational DB, we establish the conceptual model that include all entities of the whole project and the relation between them (one to many or many to many) then based on the entities we create tables and start developing the app based on the model, but now i'm lost with this new methodology of DB,
between us i really found this document DB very useful and easy but i'm still unable to put my feet on the right way -
@IT-ADMIN said:
between us i really found this document DB very useful and easy but i'm still unable to put my feet on the right way
I think that you are overthinking it. Try taking the data that you have and instead of thinking of a place for each "type" of data, make a single document for a single user/person and put all of the necessary data into that document. The data remains related by the nature of existing within a single document. If you look at the data that you have in a relational design, you can assemble a document by doing a join on it. Instead of data all over to assemble to a user, start with the data in one place.
And try not starting with the database, start with the application. You don't need to design the database at this stage.
