The choice of database depends largely on the context in which you're going to use it. There are many different things that make up the context for use. How many users do you expect will be accessing the data? What kind of data are you dealing? How is the data structured? What kind of operations are you going to perform on the data? What kind of admin capabilities do you have? What are the performance parameters? What skills does the development team that will be programming to this database have? Do they have more experience with any particular database(s)? And many more...
So, you can't expect to get a good answer to an open-ended question like that if you don't provide more context.
The best ideas are the crazy ones. If you have a crazy idea and it works, it's really valuable.—Kent Beck
Choose for what purpose? Assuming that you'll be a developer -and not a DBA- some of those are very similar (MySQL, Postgres and SQLServer). If you used one as a developer, you'll be able to use the other ones.
mongoDB is not a SQL DB, so that's a very different beast from a developer perspective.
SQLite is a SQL DB, but frequently used as an embedded DB (for example, on Android) - so the use cases for it are a bit different.
Please explain why your new employer wants you to choose two databases programs.
posted 1 year ago
They are taking me as a full stack developer. I know Java programming but they also want me to know some databases,that I will learn from scratch,and I don't know for which context they want me to know and may be depending upon the choice of the databases they will put me in particular team, I am a student and I don't know the working of IT sector, so all I can ask now is which databases is having good scope in future.
Well, who knows what the future will hold? Software development is constantly evolving, so you'll need to keep learning whatever you do.
I suggest a general purpose open source SQL DB (either MySQL or Postgres) and a document DB like MongoDB.
posted 1 year ago
If they want you to know databases, I suggest you start by asking them to train you. Consider asking what they would recommend.
Although they are an old‑fashioned paradigm, try a common‑or‑garden SQL relational database. More people use the conventional type of database than the newer‑fangled things. In which case maybe try Oracle or Postgres or MySQL.
As stated the first steps would be deciding if you need a relational database management system system (RDBMS) like MySQL, MS SQL Server or Postgre or if you would need a NoSQL system like MongoDB.
RDBMS have been around for decades and usually does a very good job with structured data.
Often times you will end up using some SQL (Structured Query Language) command for manipulating the data.
NoSQL systems, which actually means Not Only Structured Query Languages, are usually used for unstructured data.
Most NoSQL systems have their own proprietary commands for manipulating the data which could vary a fair amount between systems.
In today's world we have a lot of both structured and unstructured data, both of which are increasing daily.
A system/site like a WordPress site would probably have a lot more structured data then unstructured data and therefor would probably use a RDBMS.
Project management solutions like Trello would probably use NoSQL to store the much of their data which is probably unstructured.
“The strongest of all warriors are these two — Time and Patience.” ― Leo Tolstoy, War and Peace
posted 1 year ago
Sorry for late reply and thanks for providing your thoughts. I selected MySQL and MongoDB.
On my planet I'm considered quite beautiful. Thanks to the poetry in this tiny ad: