Amazon S3 (Simple Storage Service) vs. MongoDB

For archiving old data that is infrequently accessed it is perfect. You can choose to let it go into cold/glacier storage which saves even further costs but at the expense of accessibility. I like that you can set access rules to automatically move it to the next storage tier after a certain amount of time that it has not been accessed. I also use it a lot with PHP via the API. We have some custom in-house applications that have a fair amount of data uploaded into them. S3 has been a perfect solution to store these files, taking the load off web servers and never having issues with running out of storage.

Incentivized

MongoDB [is] great at storing JSON data grouped into "collections". In this format, you can store any JSON documents and conveniently categorize them by collections. The JSON document contained in MongoDB is called binary JSON or BSON and, like any other document in this format, is unstructured. Therefore, unlike traditional DBMS, any kind of data can be stored in collections, and this flexibility is combined with the horizontal scalability of the database. It should be noted that MongoDB does not have links between documents and “collections” (this is partially compensated by the Database Reference - links in the DBMS, but this does not completely solve the problem). As a result, a situation arises in which there is a certain set of data that is not related to other information in the database, and there is no way to combine data from different documents. In SQL systems, this would be an elementary task.

• Reliable and secure way to store objects in cloud: Storing any type of file(text, pdf, doc, csv, etc) is very easy with S3. Fetching this stored content as and when you require is also pretty easy and can be done using both the console and AWS CLI. Appropriate permissions can be set up for buckets using IAM roles/policies.
• Versioning in buckets: S3 gives you a very handy feature to store multiple versions of objects stored in a bucket.
• Lifecycle policies: You can set up lifecycle policies in S3 that can move your older objects to IA or Glacier. This setup is very easy and can be done within minutes for a bucket.
• Replication: The cross-region replication that S3 provides is wonderful. Beware of the inter-regional data transfer costs though.

Incentivized

• Easy to learn. When I picked up MongoDB for the first time, I had little background in database management or modeling. If you have a background in javascript (and JSON)... then you can figure out how to use MongoDB pretty fast.
• Fast performance.
• It's relatively easy to set up in certain environments because there are lots of ready-made solutions out there.
• There's a lot of support in the existing ecosystem for it —, especially in the node.js realm.
• Query syntax is pretty simple to grasp and utilize.
• Aggregate functions are powerful.
• Scaling options.
• Documentation is quite good and versioned for each release.

Incentivized

• The biggest problem is to rename the bucket. There is no direct way to do it. One need to copy entire content to the different bucket with intended bucket name and then remove the old bucket. Sometimes it creates issues.
• There is no direct way to upload .zip file and extract it to inside the bucket.
• While uploading large files, sometimes you will find a drop of upload speed. I observe it so many times and while checking my internet speed, I find it absolutely perfect. So there must have something wrong on the AWS side.

Incentivized

• I love the idea of Map-Reduce native support in MongoDB. Admittedly I have not used it as much as I would like -- it always seems to trip me up.
• Recent additions to the aggregation queries have helped reduce (no pun intended) my need to better wield the weapon that is Map-Reduce.

Incentivized

Due to princing, availability and scalability.

Incentivized

MongoDB is one of the most famous non-relational databases in the world, there are famous active projects that use this database. I think that the same company that develops the database gives you the online induction totally free is something that really is very positive. Accounts with a first-class support to be able to relate the correct implementation of the database, in addition to teaching you the best practices to optimize your projects, I believe that with this decision it is more than obvious which is the best decision at the time of seeing with which database to work.

Incentivized

The UI could have some improvements (better filters) and there is a lack of some useful functionality, such as renaming an existing bucket: the latter is much needed in the context of rapidly evolving companies. Overall though, Amazon S3 (Simple Storage Service) is easy to use and to onboard people and tools to, thanks to its various APIs and flexibility.

Incentivized

It is one of the reasons why we prefer it to store documents in a JSON-style format, to access the desired document very quickly regardless of its size, to be readable by human eyes, and to be easily scalable and manageable.

Incentivized

It depends on your tier within Amazon on how great of support you get. For us we have a dedicated Point of Contact that is great in taking in what we need and discussing it with the S3 team. The best thing is features we need or suggest have a good chance of landing on their roadmap.

Incentivized

I have reached multiple times to the MongoDB community for the help and they have provided each and easy solution for every problem. Over the internet and on stack overflow many people responds over the challenges. Now this tool is very much used in every company and projects so internally many people are there to give a support.

Incentivized

While the setup and configuration of MongoDB is pretty straight forward, having a vendor that performs automatic backups and scales the cluster automatically is very convenient. If you do not have a system administrator or DBA familiar with MongoDB on hand, it's a very good idea to use a 3rd party vendor that specializes in MongoDB hosting. The value is very well worth it over hosting it yourself since the cost is often reasonable among providers.

Incentivized

S3 is the most mature simple storage service on the web. It has direct competitors from Google and Azure, as well as a bunch of other competitors that focus on different aspects. For example, Backblaze specializes on file backups, and while s3 can also be used for that, Backblaze provides a better price point in exchange for more focused functionality. S3 really shines in that it performs simple things astonishingly well, while also being flexible enough to stretch itself to other situations (data lakes, file mounts, backup/restores systems, web hosting, etc.).

Incentivized

The environment I work in is somewhat unique in that we use both MySQL and MongoDB. However, each is used for specific purposes that the other is not well suited for. MongoDB is not a relational database like MySQL, so it serves as the perfect place to dump key bits of data for quick retrieval later. This is something we can't easily do with MySQL. On this smaller database, MongoDB also lets us retrieve data more quickly with its fast and efficient querying.

Incentivized

• Allows us to store large amounts of raw traffic from data providers to allow us to view data our systems received at particular times, in order to reconstruct inputs in case of errors
• Is capable of storing very large amounts of data cheaply without material impact to our business

Incentivized

• We can make more open and flexible systems due to its easy adaptation to new evolutions in web applications.
• In the latest versions it offers support for different transactions and we could carry out real tests related to the concurrency of the application.
• MongoDB allows you to have distributed clusters, which improves the speed of the queries by reducing the latency that exists between the database cluster and the service that executes the query.

Incentivized