The Mortar blog:
Mongo was built for data storage and retrieval, and Hadoop was
written for data processing. So naturally, data processing is often
better offloaded to Hadoop. Here’s why:
- Easier, more expressive language
- Libraries to build on
- Big performance improvements
- Separate workloads mean less load
For the how part, the post recommends their own Hadoop-as-a-Service platform and a set of libraries the Mortar platform provides.
✚ While browsing the Mortar blog and website I couldn’t find any information related to the costs of transferring data. The AWS services usually have a data transfer dimension, which most often has an important impact on the total costs of a solution.
Original title and link: Integrating MongoDB and Hadoop: Why & How ( ©myNoSQL)