Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I installed Mongodb in EC2 t2.small instance with this guide. I don't know whether dedicate this instance for MonogoDB. or use this same instance for app deployment for production. Suggest me the best practice.
The 'best practice' is to run the database server on its on instance; the even better 'best practice' is to run MongoDB on a cluster of instances to give you high availability.
That said, its perfectably acceptable, imo, to run the DB and your app on the same instance for small projects with low demands where cost is an important driver, although personally I would use at least a EC2 large instance if you are going to make your instance do double-duty in this manner.
Now that you know what is 'best', only you can determine how much 'best' you can afford.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I want to know how to recover Scalar DB to another instance using Cassy backup.
Because I need a new instance for tests from the production environment.
There is no direct support in Cassy to load backups that were taken in a cluster to another cluster.
Since Cassy only manages snapshots of Cassandra, you can follow the doc to do it.
For testing, I would recommend dumping some of the data from the current (possibly production) cluster and load it to a new testing cluster.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
Our current Development and Production systems are PHP v5.3.10/Ubuntu 12.04 environment. We Our new environment will be PHP Version 7.0.30/Ubuntu 16.04.
Is there a way to analyze our current PHP5.3 code and determine the scope of how much work would be needed once we port current code into our new PHP7.0 environment?
This will help give us a feel for how much work will be required to migrate from PHP5.3 to PHP7.0.
The performance is the big plus in PHP7, but the effort to migrate to it depends from your time/money and the traffic in the website, if it is heavy you should consider the migration as a real option.
For security reasons, maintenance, lots of important deprecated function, and the new cloud hosting services, I recommend to not use PHP5.3. Migrate to PHP5.6, can be a sooner solution for future problems. In the last days I have been experimenting hosting problems with mysql_connect(This extension was deprecated in PHP 5.5.0) function used in PHP5.3, and this is just an example
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I am considering using mongo db (it could be postgresql or any other ) as a data warehouse, my concern is that up to twenty or more users could be running queries at a time and this could have serious implications in terms of performance.
My question is what is the best approach to handle this in a cloud based and non cloud based environment? Do cloud based db's automatically handle this? If so would the data be consistent through all instances if a refresh on the data was made? In a non cloud based environment would the best approach be to load balance all instances? Again how would you ensure data integrity for all instances?
thanks in advance
I think auto sharding is what I am looking for
http://docs.mongodb.org/v2.6/MongoDB-sharding-guide.pdf
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
What abilites have firebird to use it in highloaded projects?
Whats better PostgreSQL or FireBirdSQL?
Any one know big projects which work with Firebird database and developed over it?
Both Firebird and PostgreSQL are good choices. I think 'better' is highly subjective and not easy to answer for such a broad and unspecific question. The case-studies on firebirdsql.org lists some projects that might be of interest to you.
It is however important to keep in mind that performance in general depends largely on the way your system interacts with the database, transaction management (and transaction configuration), underlying server etc.
Full disclosure: I am a developer of the Firebird JDBC driver, so I may be biased :)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
AWS published a blog post about migrating from Parse. I wonder why they suggest hosting MongoDB on MongoLab instead of hosting it directly on AWS?
What's the advantage of hosting MongoDB on MongoLab?
If you have enough experience to manage mongodb yourself, and scale on your own, i think aws instances are cheaper than any hosted mongodb service. That depends on how many servers you will have to manage based on your requirement.
And another reason, since parse is a hosted service, that blog post is mostly for people looking for another hosted service.