Doubt about the structure of the Nodejs + Mongo app in Digital Ocean

Asked

Viewed 143 times

0

Guys by indications I started using 1 machine at Digital Ocean in place at UOL Host. As I don’t have much experience with the server setup part, I’m in doubt and hope someone will help me:

Setting:

1) My application is running on Digital Ocean on 1 New York server.

2) My Mongodb database is running on 1 UOL Host remote machine. Is that in your opinion bad? Because of the delay in accessing the bank and so on.

Do you recommend I install Mongodb on the machine my application is on, or can this slow down my application’s server? and in that case it would be better to leave it the way it is?

Remembering that my app he uses Node only to access the webservice and has no extra processing, IE, It is very light the part of Node, basically just consume services that go straight in the BD and back the result the way I need.

  • I’m kind of a layman on this part, but I don’t see any problem leaving the bank with the server, so I think the biggest reason to do this is the size of the app, so if you have millions of hits per hour, that could be an advantage. but as I said is not very my area.

  • In this scenario, if the connection between the Node server and the BD is too slow it may be a problem. You need to analyze whether data volume requires a dedicated BD server or not.

1 answer

0

Mongodb on the application’s own base server

Running your own database is more interesting under the following aspect:

Absolute control under the database and the data entered in it

Possibility of a debug personalized

Shorter response time between operations

Possibility of a schedule that accompanies the needs of the project

Bandwidth saving of your application’s website (in the case of big-data)


Mongodb on a remote server

However professional services with excellence in tools are affordable at a low cost nowadays.

It may be interesting to plan the application for the future under these aspects:

Simplified administrative tools (or even by graphical interface)

Easy replication of the database

Easy operation of upgrade

Management of logs

Ability to add administrators


A droplet 512 RAM base and a 1GHz Core and limited disk (20GB) may not figure in the best scenario to run your own mongodb since measures like Gigabytes can be reached quickly if the application processes a lot of data.

But if your droplet have higher specifications already have to consider using your own database. In addition to a disk scheduling (SSD) it is already possible at the low cost of $10.00 per additional 100GB.

Browser other questions tagged

You are not signed in. Login or sign up in order to post.