Lots of people here are shitting on mongodb(maybe rightly so). But I think the biggest problem is that the developers making the decision on what kind of DB to use just do not understand these tools.
I always recommend reading Designing Data Intensive Applications as soon as you have an inkling that you will be asked to make such decisions in the near future.
Yesterday, https://news.ycombinator.com/item?id=15428526 hit number 1 on HN. Having read the two books, I strongly believe that they not only complement each other, but also must be required reading for any data engineer.
Basically, we improved a shell scripts based ETLs with lambdas. Now we barely can maintain them, and when a something breaks, it takes an engineer an inordinate amount of energy and time to get them fixed.
Since we process about 0.5 to 1.5 TB of time series(IOT) I was thinking about an architecture that combine AWS kinesis and airflow
Am I the only one to cry out bullshit! The guy is a terrorist, period. He deserves to pay for what he did. I survived a genocide and you don't see me go around and kill people.
Both. It seems to me in the last 12 months or so, the value of niche online community has skyrocketed. For a company like google, what is the value add of these communities?
My two cents is 1.Keep your job and hack on your projects at night/weekends. 2. You'll make better decisions for your projects/businesses when you are not worried about how to pay rent.
3.Use Steve Blank's startup manual to validate your idea before you even write one line of code.
Good luck