Alternatives to ClearDB logo

Alternatives to ClearDB

MySQL, Heroku Postgres, JAWS, Firebase, and Amazon RDS are the most popular alternatives and competitors to ClearDB.
20
19
+ 1
28

What is ClearDB and what are its top alternatives?

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.
ClearDB is a tool in the SQL Database as a Service category of a tech stack.

ClearDB alternatives & related posts

MySQL logo

MySQL

23.9K
18.5K
3.7K
23.9K
18.5K
+ 1
3.7K
The world's most popular open source database
MySQL logo
MySQL
VS
ClearDB logo
ClearDB

related MySQL posts

Tim Abbott
Tim Abbott
Founder at Zulip · | 21 upvotes · 118K views
atZulipZulip
PostgreSQL
PostgreSQL
MySQL
MySQL
Elasticsearch
Elasticsearch

We've been using PostgreSQL since the very early days of Zulip, but we actually didn't use it from the beginning. Zulip started out as a MySQL project back in 2012, because we'd heard it was a good choice for a startup with a wide community. However, we found that even though we were using the Django ORM for most of our database access, we spent a lot of time fighting with MySQL. Issues ranged from bad collation defaults, to bad query plans which required a lot of manual query tweaks.

We ended up getting so frustrated that we tried out PostgresQL, and the results were fantastic. We didn't have to do any real customization (just some tuning settings for how big a server we had), and all of our most important queries were faster out of the box. As a result, we were able to delete a bunch of custom queries escaping the ORM that we'd written to make the MySQL query planner happy (because postgres just did the right thing automatically).

And then after that, we've just gotten a ton of value out of postgres. We use its excellent built-in full-text search, which has helped us avoid needing to bring in a tool like Elasticsearch, and we've really enjoyed features like its partial indexes, which saved us a lot of work adding unnecessary extra tables to get good performance for things like our "unread messages" and "starred messages" indexes.

I can't recommend it highly enough.

See more
Julien DeFrance
Julien DeFrance
Principal Software Engineer at Tophatter · | 16 upvotes · 515.8K views
atSmartZipSmartZip
Rails
Rails
Rails API
Rails API
AWS Elastic Beanstalk
AWS Elastic Beanstalk
Capistrano
Capistrano
Docker
Docker
Amazon S3
Amazon S3
Amazon RDS
Amazon RDS
MySQL
MySQL
Amazon RDS for Aurora
Amazon RDS for Aurora
Amazon ElastiCache
Amazon ElastiCache
Memcached
Memcached
Amazon CloudFront
Amazon CloudFront
Segment
Segment
Zapier
Zapier
Amazon Redshift
Amazon Redshift
Amazon Quicksight
Amazon Quicksight
Superset
Superset
Elasticsearch
Elasticsearch
Amazon Elasticsearch Service
Amazon Elasticsearch Service
New Relic
New Relic
AWS Lambda
AWS Lambda
Node.js
Node.js
Ruby
Ruby
Amazon DynamoDB
Amazon DynamoDB
Algolia
Algolia

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
Heroku Postgres logo

Heroku Postgres

260
151
37
260
151
+ 1
37
Heroku's Database-as-a-Service. Based on the most powerful open-source database, PostgreSQL
Heroku Postgres logo
Heroku Postgres
VS
ClearDB logo
ClearDB

related Heroku Postgres posts

Amazon EC2
Amazon EC2
PostgreSQL
PostgreSQL
Amazon EBS
Amazon EBS
Amazon RDS for PostgreSQL
Amazon RDS for PostgreSQL
Heroku Postgres
Heroku Postgres
Amazon RDS
Amazon RDS

I could spin up an Amazon EC2 instance and install PostgreSQL myself, review latest configuration best practices, sort Amazon EBS storage for data, set up a snapshot process etc.

Alternatively I could use Amazon RDS, Amazon RDS for PostgreSQL or Heroku Postgres and have most of that work handled for me, by a team of world experts...

See more
Tim Nolet
Tim Nolet
Founder, Engineer & Dishwasher at Checkly · | 10 upvotes · 44.1K views
atChecklyHQChecklyHQ
PostgreSQL
PostgreSQL
Heroku
Heroku
Heroku Postgres
Heroku Postgres
Node.js
Node.js
Knex.js
Knex.js

PostgreSQL Heroku Heroku Postgres Node.js Knex.js

Last week we rolled out a simple patch that decimated the response time of a Postgres query crucial to Checkly. It quite literally went from an average of ~100ms with peaks to 1 second to a steady 1ms to 10ms.

However, that patch was just the last step of a longer journey:

  1. I looked at what API endpoints were using which queries and how their response time grew over time. Specifically the customer facing API endpoints that are directly responsible for rendering the first dashboard page of the product are crucial.

  2. I looked at the Heroku metrics such as those reported by heroku pg:outlier and cross references that with "slowest response time" statistics.

  3. I reproduced the production situation as best as possible on a local development machine and test my hypothesis that an composite index on a uuid field and a timestampz field would reduce response times.

This method secured the victory and we rolled out a new index last week. Response times plummeted. Read the full story in the blog post.

See more
JAWS logo

JAWS

4
26
0
4
26
+ 1
0
Javascript + AWS Stack – A server-free, webapp boilerplate using bleeding-edge AWS services
    Be the first to leave a pro
    JAWS logo
    JAWS
    VS
    ClearDB logo
    ClearDB

    related Firebase posts

    fontumi
    fontumi
    Firebase
    Firebase
    Node.js
    Node.js
    FeathersJS
    FeathersJS
    Vue.js
    Vue.js
    Google Compute Engine
    Google Compute Engine
    Dialogflow
    Dialogflow
    Cloud Firestore
    Cloud Firestore
    Git
    Git
    GitHub
    GitHub
    Visual Studio Code
    Visual Studio Code

    Fontumi focuses on the development of telecommunications solutions. We have opted for technologies that allow agile development and great scalability.

    Firebase and Node.js + FeathersJS are technologies that we have used on the server side. Vue.js is our main framework for clients.

    Our latest products launched have been focused on the integration of AI systems for enriched conversations. Google Compute Engine , along with Dialogflow and Cloud Firestore have been important tools for this work.

    Git + GitHub + Visual Studio Code is a killer stack.

    See more
    Aliadoc Team
    Aliadoc Team
    at aliadoc.com · | 5 upvotes · 126.8K views
    atAliadocAliadoc
    React
    React
    Create React App
    Create React App
    CloudFlare
    CloudFlare
    Firebase
    Firebase
    Cloud Functions for Firebase
    Cloud Functions for Firebase
    Google App Engine
    Google App Engine
    Google Cloud Storage
    Google Cloud Storage
    Serverless
    Serverless
    Visual Studio Code
    Visual Studio Code
    Bitbucket
    Bitbucket
    #Aliadoc

    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 RDS logo

    Amazon RDS

    5.1K
    2.8K
    757
    5.1K
    2.8K
    + 1
    757
    Set up, operate, and scale a relational database in the cloud.
    Amazon RDS logo
    Amazon RDS
    VS
    ClearDB logo
    ClearDB

    related Amazon RDS posts

    Julien DeFrance
    Julien DeFrance
    Principal Software Engineer at Tophatter · | 16 upvotes · 515.8K views
    atSmartZipSmartZip
    Rails
    Rails
    Rails API
    Rails API
    AWS Elastic Beanstalk
    AWS Elastic Beanstalk
    Capistrano
    Capistrano
    Docker
    Docker
    Amazon S3
    Amazon S3
    Amazon RDS
    Amazon RDS
    MySQL
    MySQL
    Amazon RDS for Aurora
    Amazon RDS for Aurora
    Amazon ElastiCache
    Amazon ElastiCache
    Memcached
    Memcached
    Amazon CloudFront
    Amazon CloudFront
    Segment
    Segment
    Zapier
    Zapier
    Amazon Redshift
    Amazon Redshift
    Amazon Quicksight
    Amazon Quicksight
    Superset
    Superset
    Elasticsearch
    Elasticsearch
    Amazon Elasticsearch Service
    Amazon Elasticsearch Service
    New Relic
    New Relic
    AWS Lambda
    AWS Lambda
    Node.js
    Node.js
    Ruby
    Ruby
    Amazon DynamoDB
    Amazon DynamoDB
    Algolia
    Algolia

    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
    Ganesa Vijayakumar
    Ganesa Vijayakumar
    Full Stack Coder | Module Lead · | 15 upvotes · 505K views
    Codacy
    Codacy
    SonarQube
    SonarQube
    React
    React
    React Router
    React Router
    React Native
    React Native
    JavaScript
    JavaScript
    jQuery
    jQuery
    jQuery UI
    jQuery UI
    jQuery Mobile
    jQuery Mobile
    Bootstrap
    Bootstrap
    Java
    Java
    Node.js
    Node.js
    MySQL
    MySQL
    Hibernate
    Hibernate
    Heroku
    Heroku
    Amazon S3
    Amazon S3
    Amazon RDS
    Amazon RDS
    Solr
    Solr
    Elasticsearch
    Elasticsearch
    Amazon Route 53
    Amazon Route 53
    Microsoft Azure
    Microsoft Azure
    Amazon EC2 Container Service
    Amazon EC2 Container Service
    Apache Maven
    Apache Maven
    Git
    Git
    Docker
    Docker

    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
    Amazon RDS for Aurora logo

    Amazon RDS for Aurora

    336
    161
    47
    336
    161
    + 1
    47
    MySQL and PostgreSQL compatible relational database with several times better performance
    Amazon RDS for Aurora logo
    Amazon RDS for Aurora
    VS
    ClearDB logo
    ClearDB

    related Amazon RDS for Aurora posts

    Julien DeFrance
    Julien DeFrance
    Principal Software Engineer at Tophatter · | 16 upvotes · 515.8K views
    atSmartZipSmartZip
    Rails
    Rails
    Rails API
    Rails API
    AWS Elastic Beanstalk
    AWS Elastic Beanstalk
    Capistrano
    Capistrano
    Docker
    Docker
    Amazon S3
    Amazon S3
    Amazon RDS
    Amazon RDS
    MySQL
    MySQL
    Amazon RDS for Aurora
    Amazon RDS for Aurora
    Amazon ElastiCache
    Amazon ElastiCache
    Memcached
    Memcached
    Amazon CloudFront
    Amazon CloudFront
    Segment
    Segment
    Zapier
    Zapier
    Amazon Redshift
    Amazon Redshift
    Amazon Quicksight
    Amazon Quicksight
    Superset
    Superset
    Elasticsearch
    Elasticsearch
    Amazon Elasticsearch Service
    Amazon Elasticsearch Service
    New Relic
    New Relic
    AWS Lambda
    AWS Lambda
    Node.js
    Node.js
    Ruby
    Ruby
    Amazon DynamoDB
    Amazon DynamoDB
    Algolia
    Algolia

    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
    Tim Specht
    ‎Co-Founder and CTO at Dubsmash · | 13 upvotes · 64K views
    atDubsmashDubsmash
    PostgreSQL
    PostgreSQL
    Heroku
    Heroku
    Amazon RDS
    Amazon RDS
    Amazon DynamoDB
    Amazon DynamoDB
    Redis
    Redis
    Amazon RDS for Aurora
    Amazon RDS for Aurora
    #SqlDatabaseAsAService
    #NosqlDatabaseAsAService
    #Databases
    #PlatformAsAService

    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

    252
    131
    44
    252
    131
    + 1
    44
    Store and manage data using a fully-managed, relational MySQL database
    Google Cloud SQL logo
    Google Cloud SQL
    VS
    ClearDB logo
    ClearDB

    related Google Cloud SQL posts

    Ido Shamun
    Ido Shamun
    at The Elegant Monkeys · | 5 upvotes · 5.8K views
    atDailyDaily
    MySQL
    MySQL
    Node.js
    Node.js
    Go
    Go
    Google Cloud SQL
    Google Cloud SQL
    #Backend

    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
    DigitalOcean Managed Databases logo

    DigitalOcean Managed Databases

    23
    25
    0
    23
    25
    + 1
    0
    Fully hosted and managed database engines for your applications, so you can focus on building, not patching
      Be the first to leave a pro
      DigitalOcean Managed Databases logo
      DigitalOcean Managed Databases
      VS
      ClearDB logo
      ClearDB
      Azure Database for MySQL logo

      Azure Database for MySQL

      15
      18
      0
      15
      18
      + 1
      0
      Managed MySQL database service for app developers
        Be the first to leave a pro
        Azure Database for MySQL logo
        Azure Database for MySQL
        VS
        ClearDB logo
        ClearDB
        Books logo

        Books

        6
        11
        0
        6
        11
        + 1
        0
        An immutable double-entry accounting database service (by Square)
          Be the first to leave a pro
          Books logo
          Books
          VS
          ClearDB logo
          ClearDB
          TempoDB logo

          TempoDB

          2
          1
          0
          2
          1
          + 1
          0
          Store & analyze time series data from sensors, smart meters, servers & more
            Be the first to leave a pro
            TempoDB logo
            TempoDB
            VS
            ClearDB logo
            ClearDB
            Rackspace Cloud Database logo

            Rackspace Cloud Database

            2
            3
            0
            2
            3
            + 1
            0
            Get a performance-optimized database for your application in minutes
              Be the first to leave a pro
              Rackspace Cloud Database logo
              Rackspace Cloud Database
              VS
              ClearDB logo
              ClearDB