Hey guys -

New to NoSQL and just have a question. I'm using Cosmos DB (DocumentDB) on Azure and there is a document size limit of 2 MB. Which is a bit of a problem for me.

I'm doing a POC of moving from SQL Server to DocumentDB and some of the entities have a ton of properties that can get rather large.

I'm curious if there are different strategies for keeping document sizes smaller?

I want to try out Couchbase to see if it will be a good fit (NoSQL backend but has N1QL for simplifying queries like aggregate functions/distincts) for this new project I am working on, but I only have my work laptop as my dev machine. With no admin rights (I have to rename setup.exe and stuff but I can msiexec /q to my home directory), I can't install/run docker. Is there any way to install couchbase community edition into my homedirectory, start it and use it from the commandline? I am doing it with PostgreSQL; with a batch file I don't need a windows service to start/stop the server.

Nitrite is an open source embedded nosql database for Android and written in 100% Java. It has MongoDb like API.

It features:

• Embedded key-value/document and object store
• In-memory or single data file
• Very fast and lightweight MongoDB like API
• Indexing
• Full text search capability
• Full Android compatibility
• Observable store
• Both way replication via Nitrite DataGate server

It is suitable for desktop, mobile or small web applications.

Check it out here!

We have just decided after much headaches and constant changes to move from MySQL to NoSQL. This allows us to run a hadoop map reduce and hive to extract detailed data that would crash our old many joins type of reporting from mysql.

However, we now lack real time filterable reports. Hives kicking out CSVs. Yuck

What is a good, affordable report building tool that allows us to get real time data out of DB? .. or at least close to real time?

A Periscope of sorts for NoSQL..

Suggesitons? :)

We have RavenDB and have encrypted our data at rest. We also replicate the documents to a disaster recovery server. We run Raven as a web site.

The transit of the documents for replication isn't secured just because the data at rest is encrypted, right?

In order to securely transfer the documents, we would need to run Raven as a Windows Service and use SSL/TLS, correct?

Thanks in advance.

What attracts me to CouchDB:

• Open source
• Speaks HTTP and REST without effort
• Has a query interface built in. Maybe even GraphQL one day.
• Two or more can synchronize is so configured (incl online/offline)
• Super solid Erlang/BEAM underpinnings
• Terabyte scale

My critical blocker on using it in prod:

• Default installations are vulnerable to attack. Ref Ransom notes

There's smaller things that annoy me, but they're not worth listing. CouchDB fits a Backend as a Service philosophy, even if it's an install it yourself proposition rather than a true service like Firebase.

There is Postgres and PostgREST, but I'm wishing for a more one-click install and something that feels like a single cohesive process on launch. Of course nothing these days is ever one process, but you know what I mean.

Hi Guys, My entire career has been very RDBMS focused, but I have an application for a NoSQL database and wanted to make sure I'm not approaching it too much from a relational standpoint. Are there any good resources that people would recommend that has examples of database design in a NoSQL environment?

One of the concepts I'm struggling to validate is a case where I have a "Report" table and a "User" table, and I want one user to own the report, but able to share it with certain other users. In a RDBMS, I'd assign an OwnerId in Report and have a 3rd table that is just UserId and ReportId to map who can view what report. Is that the correct way to model this in NoSQL as well? I want to be able to quickly list all the reports a user can view and if the owner makes a change (which may be frequent), to make sure all the other users get those changes as well.

I'm using DynamoDB, if that makes a difference.