Alternatives to Azure Storage logo

Alternatives to Azure Storage

Azure Redis Cache, Amazon S3, Azure Cosmos DB, OneDrive, and Dropbox are the most popular alternatives and competitors to Azure Storage.
911
744
+ 1
51

What is Azure Storage and what are its top alternatives?

Azure Storage provides the flexibility to store and retrieve large amounts of unstructured data, such as documents and media files with Azure Blobs; structured nosql based data with Azure Tables; reliable messages with Azure Queues, and use SMB based Azure Files for migrating on-premises applications to the cloud.
Azure Storage is a tool in the Cloud Storage category of a tech stack.

Top Alternatives to Azure Storage

  • Azure Redis Cache
    Azure Redis Cache

    It perfectly complements Azure database services such as Cosmos DB. It provides a cost-effective solution to scale read and write throughput of your data tier. Store and share database query results, session states, static contents, and more using a common cache-aside pattern. ...

  • Amazon S3
    Amazon S3

    Amazon Simple Storage Service provides a fully redundant data storage infrastructure for storing and retrieving any amount of data, at any time, from anywhere on the web ...

  • Azure Cosmos DB
    Azure Cosmos DB

    Azure DocumentDB is a fully managed NoSQL database service built for fast and predictable performance, high availability, elastic scaling, global distribution, and ease of development. ...

  • OneDrive
    OneDrive

    Outlook.com is a free, personal email service from Microsoft. Keep your inbox clutter-free with powerful organizational tools, and collaborate easily with OneDrive and Office Online integration. ...

  • Dropbox
    Dropbox

    Harness the power of Dropbox. Connect to an account, upload, download, search, and more. ...

  • Google Cloud Storage
    Google Cloud Storage

    Google Cloud Storage allows world-wide storing and retrieval of any amount of data and at any time. It provides a simple programming interface which enables developers to take advantage of Google's own reliable and fast networking infrastructure to perform data operations in a secure and cost effective manner. If expansion needs arise, developers can benefit from the scalability provided by Google's infrastructure. ...

  • Amazon EBS
    Amazon EBS

    Amazon EBS volumes are network-attached, and persist independently from the life of an instance. Amazon EBS provides highly available, highly reliable, predictable storage volumes that can be attached to a running Amazon EC2 instance and exposed as a device within the instance. Amazon EBS is particularly suited for applications that require a database, file system, or access to raw block level storage. ...

  • Minio
    Minio

    Minio is an object storage server compatible with Amazon S3 and licensed under Apache 2.0 License ...

Azure Storage alternatives & related posts

Azure Redis Cache logo

Azure Redis Cache

55
113
4
A fully managed, open source–compatible in-memory data store
55
113
+ 1
4
PROS OF AZURE REDIS CACHE
  • 2
    Cache-cluster
  • 2
    Redis
CONS OF AZURE REDIS CACHE
    Be the first to leave a con

    related Azure Redis Cache posts

    Amazon S3 logo

    Amazon S3

    49K
    35.2K
    2K
    Store and retrieve any amount of data, at any time, from anywhere on the web
    49K
    35.2K
    + 1
    2K
    PROS OF AMAZON S3
    • 592
      Reliable
    • 493
      Scalable
    • 458
      Cheap
    • 329
      Simple & easy
    • 83
      Many sdks
    • 30
      Logical
    • 13
      Easy Setup
    • 11
      REST API
    • 11
      1000+ POPs
    • 6
      Secure
    • 4
      Easy
    • 4
      Plug and play
    • 3
      Web UI for uploading files
    • 2
      Flexible
    • 2
      GDPR ready
    • 2
      Faster on response
    • 1
      Easy integration with CloudFront
    • 1
      Easy to use
    • 1
      Plug-gable
    CONS OF AMAZON S3
    • 7
      Permissions take some time to get right
    • 6
      Takes time/work to organize buckets & folders properly
    • 5
      Requires a credit card
    • 3
      Complex to set up

    related Amazon S3 posts

    Ashish Singh
    Tech Lead, Big Data Platform at Pinterest · | 38 upvotes · 1.2M views

    To provide employees with the critical need of interactive querying, we’ve worked with Presto, an open-source distributed SQL query engine, over the years. Operating Presto at Pinterest’s scale has involved resolving quite a few challenges like, supporting deeply nested and huge thrift schemas, slow/ bad worker detection and remediation, auto-scaling cluster, graceful cluster shutdown and impersonation support for ldap authenticator.

    Our infrastructure is built on top of Amazon EC2 and we leverage Amazon S3 for storing our data. This separates compute and storage layers, and allows multiple compute clusters to share the S3 data.

    We have hundreds of petabytes of data and tens of thousands of Apache Hive tables. Our Presto clusters are comprised of a fleet of 450 r4.8xl EC2 instances. Presto clusters together have over 100 TBs of memory and 14K vcpu cores. Within Pinterest, we have close to more than 1,000 monthly active users (out of total 1,600+ Pinterest employees) using Presto, who run about 400K queries on these clusters per month.

    Each query submitted to Presto cluster is logged to a Kafka topic via Singer. Singer is a logging agent built at Pinterest and we talked about it in a previous post. Each query is logged when it is submitted and when it finishes. When a Presto cluster crashes, we will have query submitted events without corresponding query finished events. These events enable us to capture the effect of cluster crashes over time.

    Each Presto cluster at Pinterest has workers on a mix of dedicated AWS EC2 instances and Kubernetes pods. Kubernetes platform provides us with the capability to add and remove workers from a Presto cluster very quickly. The best-case latency on bringing up a new worker on Kubernetes is less than a minute. However, when the Kubernetes cluster itself is out of resources and needs to scale up, it can take up to ten minutes. Some other advantages of deploying on Kubernetes platform is that our Presto deployment becomes agnostic of cloud vendor, instance types, OS, etc.

    #BigData #AWS #DataScience #DataEngineering

    See more
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 5M views

    Our whole DevOps stack consists of the following tools:

    • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
    • Respectively Git as revision control system
    • SourceTree as Git GUI
    • Visual Studio Code as IDE
    • CircleCI for continuous integration (automatize development process)
    • Prettier / TSLint / ESLint as code linter
    • SonarQube as quality gate
    • Docker as container management (incl. Docker Compose for multi-container application management)
    • VirtualBox for operating system simulation tests
    • Kubernetes as cluster management for docker containers
    • Heroku for deploying in test environments
    • nginx as web server (preferably used as facade server in production environment)
    • SSLMate (using OpenSSL) for certificate management
    • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
    • PostgreSQL as preferred database system
    • Redis as preferred in-memory database/store (great for caching)

    The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

    • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
    • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
    • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
    • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
    • Scalability: All-in-one framework for distributed systems.
    • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
    See more
    Azure Cosmos DB logo

    Azure Cosmos DB

    523
    966
    130
    A fully-managed, globally distributed NoSQL database service
    523
    966
    + 1
    130
    PROS OF AZURE COSMOS DB
    • 28
      Best-of-breed NoSQL features
    • 22
      High scalability
    • 15
      Globally distributed
    • 14
      Automatic indexing over flexible json data model
    • 10
      Tunable consistency
    • 10
      Always on with 99.99% availability sla
    • 7
      Javascript language integrated transactions and queries
    • 6
      Predictable performance
    • 5
      High performance
    • 5
      Analytics Store
    • 2
      Rapid Development
    • 2
      No Sql
    • 2
      Auto Indexing
    • 2
      Ease of use
    CONS OF AZURE COSMOS DB
    • 17
      Pricing
    • 4
      Poor No SQL query support

    related Azure Cosmos DB posts

    We have an in-house build experiment management system. We produce samples as input to the next step, which then could produce 1 sample(1-1) and many samples (1 - many). There are many steps like this. So far, we are tracking genealogy (limited tracking) in the MySQL database, which is becoming hard to trace back to the original material or sample(I can give more details if required). So, we are considering a Graph database. I am requesting advice from the experts.

    1. Is a graph database the right choice, or can we manage with RDBMS?
    2. If RDBMS, which RDMS, which feature, or which approach could make this manageable or sustainable
    3. If Graph database(Neo4j, OrientDB, Azure Cosmos DB, Amazon Neptune, ArangoDB), which one is good, and what are the best practices?

    I am sorry that this might be a loaded question.

    See more
    Stephen Gheysens
    Lead Solutions Engineer at Inscribe · | 6 upvotes · 24.8K views

    Hi Mohamad, out of these two options, I'd recommend starting with MongoDB (on MongoDB Atlas) for a few reasons:

    • Open Source & Portability - With MongoDB being open source, you have transparency into how your system will work. Not only can you see how it works, but you later have the option to migrate to self-hosted versions of the platform (decreasing costs and avoiding vendor lock-in) or move to a Mongo-compatible hosted database like Amazon DocumentDB or Azure Cosmos DB.

    • Querying & Aggregation - MongoDB has been around a few years longer than Firebase, and in my opinion, that is evident from the great design and flexibility of APIs you have for querying and aggregating data.

    • Tooling - MongoDB Atlas monitoring tools and the Compass GUI are great for understanding and interacting with the data in your database as you're growing your platform.

    I hope this helps!

    See more
    OneDrive logo

    OneDrive

    251
    171
    4
    Save your files and photos to OneDrive and get them from any device, anywhere
    251
    171
    + 1
    4
    PROS OF ONEDRIVE
    • 1
      Back up
    • 1
      Simple
    • 1
      FREE
    • 1
      Stable service
    CONS OF ONEDRIVE
      Be the first to leave a con

      related OneDrive posts

      Dropbox logo

      Dropbox

      21.3K
      16.5K
      1.6K
      Build the power of Dropbox into your apps
      21.3K
      16.5K
      + 1
      1.6K
      PROS OF DROPBOX
      • 432
        Easy to work with
      • 254
        Free
      • 215
        Popular
      • 175
        Shared file hosting
      • 168
        'just works'
      • 100
        No brainer
      • 79
        Integration with external services
      • 76
        Simple
      • 49
        Good api
      • 38
        Least cost (free) for the basic needs case
      • 10
        It just works
      • 7
        Convenient
      • 6
        Accessible from all of my devices
      • 5
        Command Line client
      • 4
        Can even be used by your grandma
      • 3
        Mac app
      • 3
        Sync API
      • 3
        Synchronizing laptop and desktop - work anywhere
      • 2
        Reliable
      • 2
        Cross platform app
      • 2
        Extended version history
      • 2
        Beautiful UI
      • 2
        Delta synchronization
      • 2
        Ability to pay monthly without losing your files
      • 1
        Easy/no setup
      • 1
        YC Company
      • 1
        Everybody needs to share and synchronize files reliably
      • 1
        Backups, local and cloud
      • 1
        The more the merrier
      • 1
        For when client needs file without opening firewall
      • 1
        Easy to work with
      • 1
        Everybody needs to share and synchronize files reliabl
      • 1
        Easy to use
      • 1
        So easy
      • 1
        What a beautiful app
      • 0
        The more the merrier
      CONS OF DROPBOX
      • 3
        Personal vs company account is confusing
      • 1
        Replication kills CPU and battery

      related Dropbox posts

      Shared insights
      on
      BoxBoxDropboxDropboxKloudlessKloudless

      Anyone recommend a good connector like Kloudless for connecting a SaaS app to Dropbox/Box etc? Cheers

      See more
      Jorge Cortell

      We originally used Dropbox as an easy way to store and share documents, but moved to the much more powerful and convenient Google Drive, although we still use Dropbox occasionally.

      See more
      Google Cloud Storage logo

      Google Cloud Storage

      1.5K
      1.1K
      74
      Durable and highly available object storage service
      1.5K
      1.1K
      + 1
      74
      PROS OF GOOGLE CLOUD STORAGE
      • 28
        Scalable
      • 19
        Cheap
      • 14
        Reliable
      • 9
        Easy
      • 3
        Chealp
      • 1
        More praticlal and easy
      CONS OF GOOGLE CLOUD STORAGE
        Be the first to leave a con

        related Google Cloud Storage posts

        Aliadoc Team

        In #Aliadoc, we're exploring the crowdfunding option to get traction before launch. We are building a SaaS platform for website design customization.

        For the Admin UI and website editor we use React and we're currently transitioning from a Create React App setup to a custom one because our needs have become more specific. We use CloudFlare as much as possible, it's a great service.

        For routing dynamic resources and proxy tasks to feed websites to the editor we leverage CloudFlare Workers for improved responsiveness. We use Firebase for our hosting needs and user authentication while also using several Cloud Functions for Firebase to interact with other services along with Google App Engine and Google Cloud Storage, but also the Real Time Database is on the radar for collaborative website editing.

        We generally hate configuration but honestly because of the stage of our project we lack resources for doing heavy sysops work. So we are basically just relying on Serverless technologies as much as we can to do all server side processing.

        Visual Studio Code definitively makes programming a much easier and enjoyable task, we just love it. We combine it with Bitbucket for our source code control needs.

        See more
        Amazon EBS logo

        Amazon EBS

        672
        525
        82
        Block level storage volumes for use with Amazon EC2 instances.
        672
        525
        + 1
        82
        PROS OF AMAZON EBS
        • 36
          Point-in-time snapshots
        • 27
          Data reliability
        • 19
          Configurable i/o performance
        CONS OF AMAZON EBS
          Be the first to leave a con

          related Amazon EBS posts

          We are looking for a centralised monitoring solution for our application deployed on Amazon EKS. We would like to monitor using metrics from Kubernetes, AWS services (NeptuneDB, AWS Elastic Load Balancing (ELB), Amazon EBS, Amazon S3, etc) and application microservice's custom metrics.

          We are expected to use around 80 microservices (not replicas). I think a total of 200-250 microservices will be there in the system with 10-12 slave nodes.

          We tried Prometheus but it looks like maintenance is a big issue. We need to manage scaling, maintaining the storage, and dealing with multiple exporters and Grafana. I felt this itself needs few dedicated resources (at least 2-3 people) to manage. Not sure if I am thinking in the correct direction. Please confirm.

          You mentioned Datadog and Sysdig charges per host. Does it charge per slave node?

          See more
          Minio logo

          Minio

          361
          566
          39
          AWS S3 open source alternative written in Go
          361
          566
          + 1
          39
          PROS OF MINIO
          • 9
            Store and Serve Resumes & Job Description PDF, Backups
          • 6
            S3 Compatible
          • 4
            Open Source
          • 4
            Simple
          • 3
            Encryption and Tamper-Proof
          • 2
            Scalable
          • 2
            Private Cloud Storage
          • 2
            Lambda Compute
          • 2
            Data Protection
          • 2
            Highly Available
          • 2
            Pluggable Storage Backend
          • 1
            Performance
          CONS OF MINIO
          • 2
            Deletion of huge buckets is not possible

          related Minio posts