Alternatives to Google Cloud Bigtable logo

Alternatives to Google Cloud Bigtable

Google Cloud Datastore, Microsoft Access, Google Cloud Spanner, MongoDB, and Google Cloud Storage are the most popular alternatives and competitors to Google Cloud Bigtable.
111
293
+ 1
23

What is Google Cloud Bigtable and what are its top alternatives?

Google Cloud Bigtable offers you a fast, fully managed, massively scalable NoSQL database service that's ideal for web, mobile, and Internet of Things applications requiring terabytes to petabytes of data. Unlike comparable market offerings, Cloud Bigtable doesn't require you to sacrifice speed, scale, or cost efficiency when your applications grow. Cloud Bigtable has been battle-tested at Google for more than 10 years—it's the database driving major applications such as Google Analytics and Gmail.
Google Cloud Bigtable is a tool in the NoSQL Database as a Service category of a tech stack.

Top Alternatives to Google Cloud Bigtable

  • Google Cloud Datastore

    Google Cloud Datastore

    Use a managed, NoSQL, schemaless database for storing non-relational data. Cloud Datastore automatically scales as you need it and supports transactions as well as robust, SQL-like queries. ...

  • Microsoft Access

    Microsoft Access

    It is an easy-to-use tool for creating business applications, from templates or from scratch. With its rich and intuitive design tools, it can help you create appealing and highly functional applications in a minimal amount of time. ...

  • Google Cloud Spanner

    Google Cloud Spanner

    It is a globally distributed database service that gives developers a production-ready storage solution. It provides key features such as global transactions, strongly consistent reads, and automatic multi-site replication and failover. ...

  • MongoDB

    MongoDB

    MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding. ...

  • 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. ...

  • 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. ...

  • Amazon DynamoDB

    Amazon DynamoDB

    With it , you can offload the administrative burden of operating and scaling a highly available distributed database cluster, while paying a low price for only what you use. ...

  • Cloud Firestore

    Cloud Firestore

    Cloud Firestore is a NoSQL document database that lets you easily store, sync, and query data for your mobile and web apps - at global scale. ...

Google Cloud Bigtable alternatives & related posts

Google Cloud Datastore logo

Google Cloud Datastore

206
307
12
A Fully Managed NoSQL Data Storage Service
206
307
+ 1
12
PROS OF GOOGLE CLOUD DATASTORE
  • 7
    High scalability
  • 2
    Serverless
  • 2
    Ability to query any property
  • 1
    Pay for what you use
CONS OF GOOGLE CLOUD DATASTORE
    Be the first to leave a con

    related Google Cloud Datastore posts

    Microsoft Access logo

    Microsoft Access

    55
    53
    0
    A database management system
    55
    53
    + 1
    0
    PROS OF MICROSOFT ACCESS
      Be the first to leave a pro
      CONS OF MICROSOFT ACCESS
        Be the first to leave a con

        related Microsoft Access posts

        Google Cloud Spanner logo

        Google Cloud Spanner

        31
        77
        1
        Fully managed, scalable, relational database service for regional and global application data
        31
        77
        + 1
        1
        PROS OF GOOGLE CLOUD SPANNER
        • 1
          Scalable
        CONS OF GOOGLE CLOUD SPANNER
          Be the first to leave a con

          related Google Cloud Spanner posts

          MongoDB logo

          MongoDB

          66.7K
          56.1K
          4.1K
          The database for giant ideas
          66.7K
          56.1K
          + 1
          4.1K
          PROS OF MONGODB
          • 826
            Document-oriented storage
          • 591
            No sql
          • 548
            Ease of use
          • 465
            Fast
          • 407
            High performance
          • 256
            Free
          • 215
            Open source
          • 180
            Flexible
          • 143
            Replication & high availability
          • 110
            Easy to maintain
          • 42
            Querying
          • 38
            Easy scalability
          • 37
            Auto-sharding
          • 36
            High availability
          • 31
            Map/reduce
          • 27
            Document database
          • 25
            Full index support
          • 25
            Easy setup
          • 16
            Reliable
          • 15
            Fast in-place updates
          • 14
            Agile programming, flexible, fast
          • 12
            No database migrations
          • 8
            Enterprise
          • 8
            Easy integration with Node.Js
          • 6
            Enterprise Support
          • 5
            Great NoSQL DB
          • 3
            Drivers support is good
          • 3
            Aggregation Framework
          • 3
            Support for many languages through different drivers
          • 2
            Awesome
          • 2
            Schemaless
          • 2
            Managed service
          • 2
            Fast
          • 2
            Easy to Scale
          • 1
            Consistent
          • 1
            Acid Compliant
          CONS OF MONGODB
          • 5
            Very slowly for connected models that require joins
          • 3
            Not acid compliant
          • 1
            Proprietary query language

          related MongoDB posts

          Jeyabalaji Subramanian

          Recently we were looking at a few robust and cost-effective ways of replicating the data that resides in our production MongoDB to a PostgreSQL database for data warehousing and business intelligence.

          We set ourselves the following criteria for the optimal tool that would do this job: - The data replication must be near real-time, yet it should NOT impact the production database - The data replication must be horizontally scalable (based on the load), asynchronous & crash-resilient

          Based on the above criteria, we selected the following tools to perform the end to end data replication:

          We chose MongoDB Stitch for picking up the changes in the source database. It is the serverless platform from MongoDB. One of the services offered by MongoDB Stitch is Stitch Triggers. Using stitch triggers, you can execute a serverless function (in Node.js) in real time in response to changes in the database. When there are a lot of database changes, Stitch automatically "feeds forward" these changes through an asynchronous queue.

          We chose Amazon SQS as the pipe / message backbone for communicating the changes from MongoDB to our own replication service. Interestingly enough, MongoDB stitch offers integration with AWS services.

          In the Node.js function, we wrote minimal functionality to communicate the database changes (insert / update / delete / replace) to Amazon SQS.

          Next we wrote a minimal micro-service in Python to listen to the message events on SQS, pickup the data payload & mirror the DB changes on to the target Data warehouse. We implemented source data to target data translation by modelling target table structures through SQLAlchemy . We deployed this micro-service as AWS Lambda with Zappa. With Zappa, deploying your services as event-driven & horizontally scalable Lambda service is dumb-easy.

          In the end, we got to implement a highly scalable near realtime Change Data Replication service that "works" and deployed to production in a matter of few days!

          See more
          Robert Zuber

          We use MongoDB as our primary #datastore. Mongo's approach to replica sets enables some fantastic patterns for operations like maintenance, backups, and #ETL.

          As we pull #microservices from our #monolith, we are taking the opportunity to build them with their own datastores using PostgreSQL. We also use Redis to cache data we’d never store permanently, and to rate-limit our requests to partners’ APIs (like GitHub).

          When we’re dealing with large blobs of immutable data (logs, artifacts, and test results), we store them in Amazon S3. We handle any side-effects of S3’s eventual consistency model within our own code. This ensures that we deal with user requests correctly while writes are in process.

          See more
          Google Cloud Storage logo

          Google Cloud Storage

          1.2K
          1K
          73
          Durable and highly available object storage service
          1.2K
          1K
          + 1
          73
          PROS OF GOOGLE CLOUD STORAGE
          • 28
            Scalable
          • 18
            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
            Google Cloud SQL logo

            Google Cloud SQL

            477
            482
            46
            Store and manage data using a fully-managed, relational MySQL database
            477
            482
            + 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

              Suman Adhikari
              Full Stack (Founder) at Peuconomia Int'l Pvt. Ltd. · | 10 upvotes · 10.3K views

              We use Go for the first-off due to our knowledge of it. Second off, it's highly performant and optimized for scalability. We run it using dockerized containers for our backend REST APIs.

              For Frontend, we use React with Next.js at vercel. We use NextJS here mostly due to our need for Server Side Rendering and easier route management.

              For Database, we use MySQL as it is first-off free and always has been in use with us. We use Google Cloud SQL from GCP that manages its storage and versions along with HA.

              All stacks are free to use and get the best juice out of the system. We also use Redis for caching for enterprise-grade apps where data retrieval latency matters the most.

              See more
              Ido Shamun
              at The Elegant Monkeys · | 5 upvotes · 29.9K 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
              Amazon DynamoDB logo

              Amazon DynamoDB

              3.2K
              2.8K
              195
              Fully managed NoSQL database service
              3.2K
              2.8K
              + 1
              195
              PROS OF AMAZON DYNAMODB
              • 62
                Predictable performance and cost
              • 56
                Scalable
              • 35
                Native JSON Support
              • 21
                AWS Free Tier
              • 7
                Fast
              • 3
                No sql
              • 3
                To store data
              • 2
                Serverless
              • 2
                No Stored procedures is GOOD
              • 1
                ORM with DynamoDBMapper
              • 1
                Elastic Scalability using on-demand mode
              • 1
                Elastic Scalability using autoscaling
              • 1
                DynamoDB Stream
              CONS OF AMAZON DYNAMODB
              • 4
                Only sequential access for paginate data
              • 1
                Scaling
              • 1
                Document Limit Size

              related Amazon DynamoDB 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
              Dmitry Mukhin

              Uploadcare has built an infinitely scalable infrastructure by leveraging AWS. Building on top of AWS allows us to process 350M daily requests for file uploads, manipulations, and deliveries. When we started in 2011 the only cloud alternative to AWS was Google App Engine which was a no-go for a rather complex solution we wanted to build. We also didn’t want to buy any hardware or use co-locations.

              Our stack handles receiving files, communicating with external file sources, managing file storage, managing user and file data, processing files, file caching and delivery, and managing user interface dashboards.

              At its core, Uploadcare runs on Python. The Europython 2011 conference in Florence really inspired us, coupled with the fact that it was general enough to solve all of our challenges informed this decision. Additionally we had prior experience working in Python.

              We chose to build the main application with Django because of its feature completeness and large footprint within the Python ecosystem.

              All the communications within our ecosystem occur via several HTTP APIs, Redis, Amazon S3, and Amazon DynamoDB. We decided on this architecture so that our our system could be scalable in terms of storage and database throughput. This way we only need Django running on top of our database cluster. We use PostgreSQL as our database because it is considered an industry standard when it comes to clustering and scaling.

              See more
              Cloud Firestore logo

              Cloud Firestore

              573
              749
              106
              NoSQL database built for global apps
              573
              749
              + 1
              106
              PROS OF CLOUD FIRESTORE
              • 14
                Cloud Storage
              • 14
                Easy to use
              • 11
                Easy setup
              • 11
                Realtime Database
              • 9
                Super fast
              • 7
                Authentication
              • 6
                Realtime listeners
              • 5
                Hosting
              • 5
                Google Analytics integration
              • 5
                Could Messaging
              • 4
                Performance Monitoring
              • 4
                Crash Reporting
              • 3
                Test Lab for Android
              • 3
                Sharing App via invites
              • 3
                Adwords, Admob integration
              • 2
                Dynamic Links (Deeplinking support)
              • 0
                Robust ALI
              CONS OF CLOUD FIRESTORE
              • 6
                Doesn't support FullTextSearch natively

              related Cloud Firestore posts

              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

              We are building a social media app, where users will post images, like their post, and make friends based on their interest. We are currently using Cloud Firestore and Firebase Realtime Database. We are looking for another database like Amazon DynamoDB; how much this decision can be efficient in terms of pricing and overhead?

              See more