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 5 years ago.
Improve this question
I am about to upgrade to the OpenShift Pro package. This will give me several choices for the file system. I have used EBS on the starter package as it is the only choice.
My question is:
What are the pros and cons of the different file systems available?
I will initially be setting up two regular web sites with low-volume traffic...
At this time, OpenShift Online, both Starter and Pro, only offer persistent volumes backed by AWS EBS volumes. You see the various Access Modes available for the different volume plug-ins in the OpenShift Documentation.
EBS backed persistent volumes(PVs) can only be mounted by a single pod. So, for example, if you had a web pod and a database pod, you would need 2 separate PVs. This reduces complexity and prevents any race conditions of multiple applications accessing the same PV at the same time.
Related
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 10 months ago.
Improve this question
I have been thinking of making a program to use in my company. I would like to store information in a (local) database and use this to keep track of the payments of my clients. I am most experienced in programming in Java. Do you have any suggestions for these databases?
I believe you are probably looking for SQLite. It is very light, basic, works with SQL,but doesn’t have any built in relational methods to link multiple tables together(JOINS, etc). As you mentioned you’ll be using Java, here’s the SQLITEJDBCPackage. Also, here’s a blog that can help you get started.
On the other hand, there is a wide variety of databases present in the market like:
RDBMS: MySQL, PostgresSQL
NoSQL: MongoDB(can run on cloud and locally), Neo4J
Time Series Database(If you storing IOT or time dependant data): InfluxDB
Cloud Databases(Might not be relevant to you since you want a local setup, but just to help you understand better): Firebase, Neo4J, MongoDB, AWS RDS, etc.
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
AMAZON VS GOOGLE
Compared to the prices and features and service
what platform should i go for if i want to host a small sql db some small apps webservice and a small storage?
What are the main differences between them?....
Has anybody experience with the these services and would like to share some Information ....
Everything is welcome!
Since you've used the word "small" 3 times, I will venture to say that, in my opinion, GAE is the best fit. Small apps remain inside the free quota on GAE, and you can't beat $0 a far as price goes. Also, GAE handles more of the messy, time-consuming backend tasks. I doubt you want to spend much time maintaining or setting up a "small" app, so having to deal with fewer of these tasks is beneficial. I have some small apps on GAE which I have not even touched for a couple of years. Time is money.
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
There is a lot of infomation scattered throughout the internet regarding this issue.
Can anyone give me an overview about clojure web app deployment? The differences between deployment in a standalone server vs a containerless aproach? The advantages and disadvantages among the different players such as Amazon's Elastic Beanstalk (EB), Heroku, Google App Engine, etc? Support for maven and lein?
Thanks!
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 9 years ago.
Improve this question
Am a beginner and wants to implement sorl for search with a mvc web application.
Witch web server is the fastest and most secure to use for sorl?
Jetty, tomcat?
Either is fine.
Solr uses Jetty to make the initial setup and configuration process easier and ships with it. But that does not mean that Jetty is a bad choice for production deployment. If your
The organization already has a standard Java web-application platform, then Solr will work
with it - Tomcat, weblogic, JBoss etc. But if you have some choice then use Jetty. It's fast,
stable, mature, and easy to administer and customize. In fact, Google uses Jetty for their
App Engine—see www.infoq.com/news/2009/08/google-chose-jetty/.
If you want to use Tomcat solr has steps to setup , its easy : http://wiki.apache.org/solr/SolrTomcat
So the answer depends, security, what your organization allows. Solr is a war file all it cares is for a Servlet Container.
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 am developing an open source CMS and have been deciding whether or not to offer support for multiple database platforms. What are your views and opinions on this matter? Should I stick with and optimize for a single platform or offer support for more?
Thanks in advance for your input.
IT depends on your plans. If you want the CMS to became popular (I meant Open Source) make it as flexible as possible with high database abstraction. I can only tell that leading PHP - based CMS "Drupal" went through path form MySQL only to all leading DBs including NoSQL.
Ceirtainly, it should. At least, it should be scalable and customizable, that's why uses may prefer different databases.
If you want more users, then yes. Some of your users might like Microsoft SQL Server. Others might find that Oracle's fathering of MySQL put other open source databases into higher regard. Same principle applies to what webservers (IIS, Apache) and web browsers you support. (IE, FireFox, Safari, Chrome, etc.)