Alternatives to DigitalOcean Managed Databases logo

Alternatives to DigitalOcean Managed Databases

Amazon RDS, Amazon Aurora, Google Cloud SQL, Azure SQL Database, and Books are the most popular alternatives and competitors to DigitalOcean Managed Databases.
46
52
+ 1
0

What is DigitalOcean Managed Databases and what are its top alternatives?

Build apps and store data in minutes with easy access to one or more databases and sleep better knowing your data is backed up and optimized.
DigitalOcean Managed Databases is a tool in the SQL Database as a Service category of a tech stack.

Top Alternatives to DigitalOcean Managed Databases

  • Amazon RDS

    Amazon RDS

    Amazon RDS gives you access to the capabilities of a familiar MySQL, Oracle or Microsoft SQL Server database engine. This means that the code, applications, and tools you already use today with your existing databases can be used with Amazon RDS. Amazon RDS automatically patches the database software and backs up your database, storing the backups for a user-defined retention period and enabling point-in-time recovery. You benefit from the flexibility of being able to scale the compute resources or storage capacity associated with your Database Instance (DB Instance) via a single API call. ...

  • Amazon Aurora

    Amazon Aurora

    Amazon Aurora is a MySQL-compatible, relational database engine that combines the speed and availability of high-end commercial databases with the simplicity and cost-effectiveness of open source databases. Amazon Aurora provides up to five times better performance than MySQL at a price point one tenth that of a commercial database while delivering similar performance and availability. ...

  • Google Cloud SQL

    Google Cloud SQL

    MySQL databases deployed in the cloud without a fuss. Google Cloud Platform provides you with powerful databases that run fast, don’t run out of space and give your application the redundant, reliable storage it needs. ...

  • Azure SQL Database

    Azure SQL Database

    It is the intelligent, scalable, cloud database service that provides the broadest SQL Server engine compatibility and up to a 212% return on investment. It is a database service that can quickly and efficiently scale to meet demand, is automatically highly available, and supports a variety of third party software. ...

  • Books

    Books

    It is an immutable double-entry accounting database service. It supports many clients and businesses at global scale, leaning on Google Cloud Spanner and Google Kubernetes Engine to make that possible. ...

  • Azure Database for MySQL

    Azure Database for MySQL

    Azure Database for MySQL provides a managed database service for app development and deployment that allows you to stand up a MySQL database in minutes and scale on the fly – on the cloud you trust most. ...

  • ClearDB

    ClearDB

    ClearDB uses a combination of advanced replication techniques, advanced cluster technology, and layered web services to provide you with a MySQL database that is "smarter" than usual. ...

  • Azure SQL Managed Instance

    Azure SQL Managed Instance

    It is the intelligent, scalable cloud database service that combines the broadest SQL Server database engine compatibility with all the benefits of a fully managed and evergreen platform as a service. ...

DigitalOcean Managed Databases alternatives & related posts

Amazon RDS logo

Amazon RDS

11.9K
7.7K
752
Set up, operate, and scale a relational database in the cloud.
11.9K
7.7K
+ 1
752
PROS OF AMAZON RDS
  • 163
    Reliable failovers
  • 154
    Automated backups
  • 129
    Backed by amazon
  • 92
    Db snapshots
  • 86
    Multi-availability
  • 29
    Control iops, fast restore to point of time
  • 27
    Security
  • 23
    Elastic
  • 20
    Automatic software patching
  • 20
    Push-button scaling
  • 4
    Replication
  • 3
    Reliable
  • 2
    Isolation
CONS OF AMAZON RDS
    Be the first to leave a con

    related Amazon RDS posts

    Ganesa Vijayakumar
    Full Stack Coder | Module Lead · | 19 upvotes · 2.5M views

    I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

    I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

    As per my work experience and knowledge, I have chosen the followings stacks to this mission.

    UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

    Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

    Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

    Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

    Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

    Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

    Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

    Happy Coding! Suggestions are welcome! :)

    Thanks, Ganesa

    See more
    John Kodumal

    As we've evolved or added additional infrastructure to our stack, we've biased towards managed services. Most new backing stores are Amazon RDS instances now. We do use self-managed PostgreSQL with TimescaleDB for time-series data—this is made HA with the use of Patroni and Consul.

    We also use managed Amazon ElastiCache instances instead of spinning up Amazon EC2 instances to run Redis workloads, as well as shifting to Amazon Kinesis instead of Kafka.

    See more
    Amazon Aurora logo

    Amazon Aurora

    670
    591
    53
    MySQL and PostgreSQL compatible relational database with several times better performance
    670
    591
    + 1
    53
    PROS OF AMAZON AURORA
    • 13
      MySQL compatibility
    • 12
      Better performance
    • 10
      Easy read scalability
    • 8
      Speed
    • 7
      Low latency read replica
    • 2
      High IOPS cost
    • 1
      Good cost performance
    CONS OF AMAZON AURORA
    • 2
      Vendor locking
    • 1
      Rigid schema

    related Amazon Aurora posts

    Julien DeFrance
    Principal Software Engineer at Tophatter · | 16 upvotes · 2.4M views

    Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

    I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

    For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

    Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

    Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

    Future improvements / technology decisions included:

    Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

    As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

    One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

    See more
    Tim Specht
    ‎Co-Founder and CTO at Dubsmash · | 13 upvotes · 102.3K views

    Over the years we have added a wide variety of different storages to our stack including PostgreSQL (some hosted by Heroku, some by Amazon RDS) for storing relational data, Amazon DynamoDB to store non-relational data like recommendations & user connections, or Redis to hold pre-aggregated data to speed up API endpoints.

    Since we started running Postgres ourselves on RDS instead of only using the managed offerings of Heroku, we've gained additional flexibility in scaling our application while reducing costs at the same time.

    We are also heavily testing Amazon RDS for Aurora in its Postgres-compatible version and will also give the new release of Aurora Serverless a try!

    #SqlDatabaseAsAService #NosqlDatabaseAsAService #Databases #PlatformAsAService

    See more
    Google Cloud SQL logo

    Google Cloud SQL

    479
    476
    46
    Store and manage data using a fully-managed, relational MySQL database
    479
    476
    + 1
    46
    PROS OF GOOGLE CLOUD SQL
    • 13
      Fully managed
    • 10
      SQL
    • 10
      Backed by Google
    • 4
      Flexible
    • 3
      Encryption at rest and transit
    • 3
      Replication across multiple zone by default
    • 3
      Automatic Software Patching
    CONS OF GOOGLE CLOUD SQL
      Be the first to leave a con

      related Google Cloud SQL posts

      Ido Shamun
      at The Elegant Monkeys · | 5 upvotes · 29.1K views

      As far as the backend goes, we first had to decide which database will power most of Daily services. Considering relational databases vs document datbases, we decided that the relational model is a better fit for Daily as we have a lot of connections between the different entities. At the time MySQL was the only service available on Google Cloud SQL so this was out choice. In terms of #backend development Node.js powers most of our services, thanks to its amazing ecosystem there are a lot of modules publicly available to shorten the development time. Go is for the light services which are all about performance and delivering quickly the response, such as our redirector service.

      See more
      Azure SQL Database logo

      Azure SQL Database

      365
      337
      7
      Managed, intelligent SQL in the cloud
      365
      337
      + 1
      7
      PROS OF AZURE SQL DATABASE
      • 3
        Managed
      • 2
        Scalable
      • 2
        Secure
      CONS OF AZURE SQL DATABASE
        Be the first to leave a con

        related Azure SQL Database posts

        Books logo

        Books

        35
        42
        0
        An immutable double-entry accounting database service (by Square)
        35
        42
        + 1
        0
        PROS OF BOOKS
          Be the first to leave a pro
          CONS OF BOOKS
            Be the first to leave a con

            related Books posts

            Azure Database for MySQL logo

            Azure Database for MySQL

            35
            80
            0
            Managed MySQL database service for app developers
            35
            80
            + 1
            0
            PROS OF AZURE DATABASE FOR MYSQL
              Be the first to leave a pro
              CONS OF AZURE DATABASE FOR MYSQL
                Be the first to leave a con

                related Azure Database for MySQL posts

                ClearDB logo

                ClearDB

                24
                68
                28
                Fault tolerant database-as-a-service in the cloud for your MySQL powered applications.
                24
                68
                + 1
                28
                PROS OF CLEARDB
                • 7
                  Cloud SQL
                • 6
                  Heroku
                • 4
                  Fast
                • 3
                  Great Backup
                • 3
                  Easy to use
                • 2
                  Scalability
                • 1
                  Master / master replication
                • 1
                  Great Support
                • 1
                  Geographic redundancy
                CONS OF CLEARDB
                  Be the first to leave a con

                  related ClearDB posts

                  Hi, I'm a beginner at using MySQL, I currently deployed my crud app on Heroku using the ClearDB add-on. I didn't see that coming, but the increased value of the primary key instead of being 1 is set to 10, and I cannot find a way to change it. Now I`m considering switching and deploying the full app and MySql to DigitalOcean any advice on that? Will I get the same issue? Thanks in advance!

                  See more
                  Azure SQL Managed Instance logo

                  Azure SQL Managed Instance

                  9
                  14
                  0
                  The intelligent, scalable cloud database service
                  9
                  14
                  + 1
                  0
                  PROS OF AZURE SQL MANAGED INSTANCE
                    Be the first to leave a pro
                    CONS OF AZURE SQL MANAGED INSTANCE
                      Be the first to leave a con

                      related Azure SQL Managed Instance posts