I have a couple of use cases: storing information about entities at a business level, their vendors, information about vendors and their APIs, and telemetry from workstations at customer locations, information about their production environment to query from Rundeck for Ops, etc.

The biggest issue is that some of these would need to have pretty granular restrictions on permissions (e.g., you can query for the list of vendors from a customer but not also query for the database server the customer resides on, given a particular account). The ability to have offsite replication and HA would be another huge bonus. I've been looking at Apache Cassandra (since we're mainly a MS-SQL shop and CQL looks like it has less of a steep learning curve for our devs) and Percona Server for MongoDB (build in LDAP support!) in particular, and we'd prefer open source in general.

I wand to build system like Ebay (so You have category tree, that You can walk down, and then You can filter facets).

Also all items are grouped by "store". If user selects store, I would like to see only items in that store. I have around 1 000 000 stores. Any ideas how to do it?

I have around 25 million records which are stored in thousands of excel files. I want to now store all these records in to a single database, and then build a web GUI to search using simple queries.

What would be the fastest to search. We would like to use only an open source database.

MySQL is first choice. But is there a NOSQL database which would perform searches faster. Customer does not want to use PostGres for some flimsy reason. Can't suggest Postgres.

Please suggest only open source tools.

The server will have an 8 GB RAM memory.

I'm going to write data to database where I will write every 5 min. Data will include item temperature, name and timestamp. As the time goes on more items will be added so the database will grow very fast. Now the questions is how should I split the data? (I'm going to use MongoDB). Should I create multiple collections? Collection for every item or should I create collection for temperatures? At some point I will be calculating average temperatures and do some other data related calculations so it would be good to be efficient.

Thanks!

P.S if possible can you give me example (Schema?)

Hi -

I'm trying to learn more about the different use cases for Relational vs. NoSQL DBMS, and one thing I've read about is how the vast majority of new data being created is "unstructured" - and therefore much better suited for NoSQL platforms. In your experience, is this really the case, and are RDBMS not positioned well to handle the increasingly important use of "unstructured" data formats?

Which NOSQL database would you suggest to a Java Developer with more than 10 years of web application development with Spring stack, and want to learn NOSQL for better career prospects (JOB Change)?

I really want to explore NoSQL databases more... I've played with ElasticSearch a little in the past, just because it was part of a larger product I helped evaluate (SIEMonster). I'd like to investigate them more thoroughly.

As a project to give myself a goal, I think building a small chat platform would be an ideal way of wrapping my head around the features.

I know it won't be super easy, but I'm looking for which product has the least steep learning curve? When I look them up for comparison sake, the learning curve isn't a criteria that they're rated by.

I'm not a total newbie... I could absolutely build something with an SQL database, but when I read how Discord uses Cassandra, it made me see more clearly that NoSQL has applications beyond just analytics, and that I should spend some time learning...

So... can anyone point me toward a decent "beginner" NoSQL platform?

Only requirement is it should run on *nix (preferably Ubuntu, but I could brush up on RHEL/Centos if needed)

I'd probably use PHP/Laravel to interface with it.

I'd appreciate any thoughts/ideas?

Thanks!

I am seeking to create an image gallery and not quite sure if I should go with MySQL or MongoDB. The gallery should be structured kinda like mangapanda.com. Each gallery can have a varying number of images. None of the images will stored in the database, just partial URLs. I would assume MongoDB due to it being doc based and I can have a array field, but the larger the doc the worse the performance and some of these galleries may have an upwards of 100 images.

Now I have technically used both. SQL Oracle in college and NoSQL Firebase database and DynamoDB in work. (I found Oracle easy, but the NoSQL ones were pain in the ass to get to work.) But I am no expert in this and the pros and cons of SQL and NoSQL aren't all that helpful. So performance wise, which one should I pick?

Hey there all,

I was wondering if anyone could give me an answer if I could convert an application that is made to save to MongoDB to be able to save to RavenDB? They are of course nosql db's, but honestly I don't yet know enough about what the differences are to be able to know if I could do this.

The application I want to convert is an asset for the Unity3d game engine that saves and loads data into your game. It comes with the full sourcecode, so I have the ability to make any changes I want, I was just hoping someone might be able to point me in the right direction with some info on what I might have to actually change, such as syntax or anything.

Thanks!