You re-wrote your entire REST API in a new language without first understanding where your performance issues were?
What's funny is how much more exciting Arduino itself is, compared to all this.
If that's legitimately your opinion on that topic then I suggest you expand your knowledge.
NoSQL databases aren't slot in replacement for SQL databases. However, for what they're good at they're REALLY good at it. Namely highly scalable, Document Storage (or "blobs"), and incredibly low latency reads.
Keep in mind that NoSQL doesn't mean schemaless. You can have a schema and be NoSQL, and that is the direction most NoSQL databases are moving into (or have moved into).
So, If my knowledge were expanded I would think NoSQL is an equally valid option, and not a worse one? I hesitate to do any more expansion because of this panel held in 2014 [0] asking weather we are in a big data bubble, and probably answering "yes", but I wasn't there.
Simple query language is REALLY good too. It has a kind of general usefulness.
> Keep in mind that NoSQL doesn't mean schemaless. You can have a schema and be NoSQL
Can you also have SQL and be NoSQL?
[0] http://people.csail.mit.edu/tatbul/publications/sigmod14_pan...
For some things NoSQL would be a better option. For most things SQL remains the better option.
> I hesitate to do any more expansion because of this panel held in 2014 [0] asking weather we are in a big data bubble, and probably answering "yes", but I wasn't there.
We were in a dot-com bubble around 97-2000, maybe the internet is a bad idea also?
> Can you also have SQL and be NoSQL?
By definition, no. But some NoSQL databases do support an alternative to SQL with some of SQL's properties (e.g. JSON-like syntax).
This is all just tech hipsterism.
Thank you! I have been looking for the right words to describe this for ages. You nailed it.