Alternatives to Heroku Redis logo

Alternatives to Heroku Redis

Redis Cloud, Redis To Go, Firebase, MySQL, and PostgreSQL are the most popular alternatives and competitors to Heroku Redis.
105
163
+ 1
5

What is Heroku Redis and what are its top alternatives?

Heroku Redis is a managed key-value store service offered by Heroku, which is fully compatible with Redis. It provides features like automated failover, data persistence, and seamless integration with Heroku applications. However, Heroku Redis has limitations such as limited support for advanced Redis features and potential performance bottlenecks at scale.

  1. Amazon ElastiCache: Amazon ElastiCache is a fully managed in-memory data store service compatible with Redis. It offers automatic scaling, high availability, and low latency performance. Pros: Seamless integration with AWS services, automated backups. Cons: Higher costs compared to self-hosted solutions.

  2. Redis Labs: Redis Labs provides a fully managed Redis service with features like multi-region replication, high availability, and real-time monitoring. Pros: Advanced features like active-active geo-distribution, on-demand scaling. Cons: Pricing might be high for small-scale deployments.

  3. Google Cloud Memorystore: Google Cloud Memorystore is a managed Redis service that offers automatic provisioning, scaling, and data replication. Pros: High availability, seamless integration with Google Cloud services. Cons: Limited to Google Cloud Platform.

  4. Microsoft Azure Cache for Redis: Azure Cache for Redis is a fully managed Redis service on the Microsoft Azure platform. It provides features like data persistence, monitoring, and clustering. Pros: Integration with Azure services, active-active geo-replication. Cons: Pricing may be higher compared to self-managed Redis instances.

  5. ScaleGrid: ScaleGrid offers a fully managed Redis service with features like automated backups, high availability, and custom monitoring. Pros: Customizable configurations, multi-cloud support. Cons: Limited free tier compared to other alternatives.

  6. Alibaba Cloud ApsaraDB for Redis: Alibaba Cloud ApsaraDB for Redis is a managed Redis service with features like data encryption, automatic failover, and high throughput. Pros: Seamless integration with Alibaba Cloud services, compliance with industry standards. Cons: Limited availability outside of Alibaba Cloud regions.

  7. MemCachier: MemCachier is a managed Memcached service that offers features like automatic failover, data persistence, and replication. Pros: Easy to use, seamless integration with popular platforms. Cons: Limited to Memcached, not compatible with Redis.

  8. Redisson: Redisson is a Java client for Redis that offers features like distributed locks, data structures, and asynchronous operations. Pros: Rich set of features, open-source. Cons: Requires integration into existing application code.

  9. Upstash: Upstash is a serverless Redis service that offers features like automatic scaling, data persistence, and multi-region replication. Pros: Serverless architecture, pay-as-you-go pricing model. Cons: Limited to Redis, no advanced features like clustering.

  10. Redislabs: Redislabs provide fully managed redis service with AI-enhanced monitoring and Anomaly detection. Pros: Advanced features like Machine learning-based monitoring, fully managed service. Cons: Higher costs compared to some other alternatives.

Top Alternatives to Heroku Redis

  • Redis Cloud
    Redis Cloud

    Redis Cloud is a fully-managed service for running your Redis dataset. It overcomes Redis’ scalability limitation by supporting all Redis commands at any dataset size. Your dataset is constantly replicated, so if a node fails, an auto-switchover mechanism guarantees data is served without interruption. ...

  • Redis To Go
    Redis To Go

    Redis To Go was created to make the managing Redis instances easier, whether it is just one instance or serveral. Deploying a new instance of Redis is dead simple, whether for production or development. ...

  • Firebase
    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • MySQL
    MySQL

    The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software. ...

  • PostgreSQL
    PostgreSQL

    PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions. ...

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

  • Redis
    Redis

    Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams. ...

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

Heroku Redis alternatives & related posts

Redis Cloud logo

Redis Cloud

71
9
Enterprise-Class Redis for Developers
71
9
PROS OF REDIS CLOUD
  • 9
    Heroku Addon
CONS OF REDIS CLOUD
    Be the first to leave a con

    related Redis Cloud posts

    Redis To Go logo

    Redis To Go

    51
    18
    Simple Redis hosting
    51
    18
    PROS OF REDIS TO GO
    • 5
      Heroku Add-on
    • 3
      Pub-Sub
    • 3
      Always up
    • 3
      Easy setup
    • 3
      Affordable
    • 1
      Perfect full sync
    CONS OF REDIS TO GO
      Be the first to leave a con

      related Redis To Go posts

      Firebase logo

      Firebase

      42.1K
      2K
      The Realtime App Platform
      42.1K
      2K
      PROS OF FIREBASE
      • 371
        Realtime backend made easy
      • 270
        Fast and responsive
      • 242
        Easy setup
      • 215
        Real-time
      • 191
        JSON
      • 134
        Free
      • 128
        Backed by google
      • 83
        Angular adaptor
      • 68
        Reliable
      • 36
        Great customer support
      • 32
        Great documentation
      • 25
        Real-time synchronization
      • 21
        Mobile friendly
      • 19
        Rapid prototyping
      • 14
        Great security
      • 12
        Automatic scaling
      • 11
        Freakingly awesome
      • 8
        Super fast development
      • 8
        Angularfire is an amazing addition!
      • 8
        Chat
      • 6
        Firebase hosting
      • 6
        Built in user auth/oauth
      • 6
        Awesome next-gen backend
      • 6
        Ios adaptor
      • 4
        Speed of light
      • 4
        Very easy to use
      • 3
        Great
      • 3
        It's made development super fast
      • 3
        Brilliant for startups
      • 2
        Free hosting
      • 2
        Cloud functions
      • 2
        JS Offline and Sync suport
      • 2
        Low battery consumption
      • 2
        .net
      • 2
        The concurrent updates create a great experience
      • 2
        Push notification
      • 2
        I can quickly create static web apps with no backend
      • 2
        Great all-round functionality
      • 2
        Free authentication solution
      • 1
        Easy Reactjs integration
      • 1
        Google's support
      • 1
        Free SSL
      • 1
        CDN & cache out of the box
      • 1
        Easy to use
      • 1
        Large
      • 1
        Faster workflow
      • 1
        Serverless
      • 1
        Good Free Limits
      • 1
        Simple and easy
      CONS OF FIREBASE
      • 31
        Can become expensive
      • 16
        No open source, you depend on external company
      • 15
        Scalability is not infinite
      • 9
        Not Flexible Enough
      • 7
        Cant filter queries
      • 3
        Very unstable server
      • 3
        No Relational Data
      • 2
        Too many errors
      • 2
        No offline sync

      related Firebase posts

      Stephen Gheysens
      Lead Solutions Engineer at Inscribe · | 14 upvotes · 1.9M views

      Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

      My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

      See more
      Eugene Cheah

      For inboxkitten.com, an opensource disposable email service;

      We migrated our serverless workload from Cloud Functions for Firebase to CloudFlare workers, taking advantage of the lower cost and faster-performing edge computing of Cloudflare network. Made possible due to our extremely low CPU and RAM overhead of our serverless functions.

      If I were to summarize the limitation of Cloudflare (as oppose to firebase/gcp functions), it would be ...

      1. <5ms CPU time limit
      2. Incompatible with express.js
      3. one script limitation per domain

      Limitations our workload is able to conform with (YMMV)

      For hosting of static files, we migrated from Firebase to CommonsHost

      More details on the trade-off in between both serverless providers is in the article

      See more
      MySQL logo

      MySQL

      128.3K
      3.8K
      The world's most popular open source database
      128.3K
      3.8K
      PROS OF MYSQL
      • 800
        Sql
      • 679
        Free
      • 562
        Easy
      • 528
        Widely used
      • 490
        Open source
      • 180
        High availability
      • 160
        Cross-platform support
      • 104
        Great community
      • 79
        Secure
      • 75
        Full-text indexing and searching
      • 26
        Fast, open, available
      • 16
        Reliable
      • 16
        SSL support
      • 15
        Robust
      • 9
        Enterprise Version
      • 7
        Easy to set up on all platforms
      • 3
        NoSQL access to JSON data type
      • 1
        Relational database
      • 1
        Easy, light, scalable
      • 1
        Sequel Pro (best SQL GUI)
      • 1
        Replica Support
      CONS OF MYSQL
      • 16
        Owned by a company with their own agenda
      • 3
        Can't roll back schema changes

      related MySQL posts

      Nick Rockwell
      SVP, Engineering at Fastly · | 46 upvotes · 4.4M views

      When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

      So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

      React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

      Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

      See more

      Hello, I am building a website for a school that's used by students to find Zoom meeting links, view their marks, and check course materials. It is also used by the teachers to put the meeting links, students' marks, and course materials.

      I created a similar website using HTML, CSS, PHP, and MySQL. Now I want to implement this project using some frameworks: Next.js, ExpressJS and use PostgreSQL instead of MYSQL

      I want to have some advice on whether these are enough to implement my project.

      See more
      PostgreSQL logo

      PostgreSQL

      100.4K
      3.5K
      A powerful, open source object-relational database system
      100.4K
      3.5K
      PROS OF POSTGRESQL
      • 764
        Relational database
      • 510
        High availability
      • 439
        Enterprise class database
      • 383
        Sql
      • 304
        Sql + nosql
      • 173
        Great community
      • 147
        Easy to setup
      • 131
        Heroku
      • 130
        Secure by default
      • 113
        Postgis
      • 50
        Supports Key-Value
      • 48
        Great JSON support
      • 34
        Cross platform
      • 33
        Extensible
      • 28
        Replication
      • 26
        Triggers
      • 23
        Multiversion concurrency control
      • 23
        Rollback
      • 21
        Open source
      • 18
        Heroku Add-on
      • 17
        Stable, Simple and Good Performance
      • 15
        Powerful
      • 13
        Lets be serious, what other SQL DB would you go for?
      • 11
        Good documentation
      • 9
        Scalable
      • 8
        Reliable
      • 8
        Intelligent optimizer
      • 8
        Free
      • 7
        Transactional DDL
      • 7
        Modern
      • 6
        One stop solution for all things sql no matter the os
      • 5
        Relational database with MVCC
      • 5
        Faster Development
      • 4
        Full-Text Search
      • 4
        Developer friendly
      • 3
        Open-source
      • 3
        search
      • 3
        Great DB for Transactional system or Application
      • 3
        Free version
      • 3
        Excellent source code
      • 3
        Relational datanbase
      • 2
        Text
      • 2
        Full-text
      • 1
        Can handle up to petabytes worth of size
      • 1
        Multiple procedural languages supported
      • 1
        Composability
      • 0
        Native
      CONS OF POSTGRESQL
      • 10
        Table/index bloatings

      related PostgreSQL posts

      Hello, I am building a website for a school that's used by students to find Zoom meeting links, view their marks, and check course materials. It is also used by the teachers to put the meeting links, students' marks, and course materials.

      I created a similar website using HTML, CSS, PHP, and MySQL. Now I want to implement this project using some frameworks: Next.js, ExpressJS and use PostgreSQL instead of MYSQL

      I want to have some advice on whether these are enough to implement my project.

      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 12.7M 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
      MongoDB logo

      MongoDB

      95.1K
      4.1K
      The database for giant ideas
      95.1K
      4.1K
      PROS OF MONGODB
      • 829
        Document-oriented storage
      • 594
        No sql
      • 554
        Ease of use
      • 465
        Fast
      • 410
        High performance
      • 255
        Free
      • 219
        Open source
      • 180
        Flexible
      • 145
        Replication & high availability
      • 112
        Easy to maintain
      • 42
        Querying
      • 39
        Easy scalability
      • 38
        Auto-sharding
      • 37
        High availability
      • 31
        Map/reduce
      • 27
        Document database
      • 25
        Easy setup
      • 25
        Full index support
      • 16
        Reliable
      • 15
        Fast in-place updates
      • 14
        Agile programming, flexible, fast
      • 12
        No database migrations
      • 8
        Easy integration with Node.Js
      • 8
        Enterprise
      • 6
        Enterprise Support
      • 5
        Great NoSQL DB
      • 4
        Support for many languages through different drivers
      • 3
        Schemaless
      • 3
        Aggregation Framework
      • 3
        Drivers support is good
      • 2
        Fast
      • 2
        Managed service
      • 2
        Easy to Scale
      • 2
        Awesome
      • 2
        Consistent
      • 1
        Good GUI
      • 1
        Acid Compliant
      CONS OF MONGODB
      • 6
        Very slowly for connected models that require joins
      • 3
        Not acid compliant
      • 2
        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
      Redis logo

      Redis

      60.6K
      3.9K
      Open source (BSD licensed), in-memory data structure store
      60.6K
      3.9K
      PROS OF REDIS
      • 887
        Performance
      • 542
        Super fast
      • 514
        Ease of use
      • 444
        In-memory cache
      • 324
        Advanced key-value cache
      • 194
        Open source
      • 182
        Easy to deploy
      • 165
        Stable
      • 156
        Free
      • 121
        Fast
      • 42
        High-Performance
      • 40
        High Availability
      • 35
        Data Structures
      • 32
        Very Scalable
      • 24
        Replication
      • 23
        Pub/Sub
      • 22
        Great community
      • 19
        "NoSQL" key-value data store
      • 16
        Hashes
      • 13
        Sets
      • 11
        Sorted Sets
      • 10
        Lists
      • 10
        NoSQL
      • 9
        Async replication
      • 9
        BSD licensed
      • 8
        Integrates super easy with Sidekiq for Rails background
      • 8
        Bitmaps
      • 7
        Open Source
      • 7
        Keys with a limited time-to-live
      • 6
        Lua scripting
      • 6
        Strings
      • 5
        Awesomeness for Free
      • 5
        Hyperloglogs
      • 4
        Runs server side LUA
      • 4
        Transactions
      • 4
        Networked
      • 4
        Outstanding performance
      • 4
        Feature Rich
      • 4
        Written in ANSI C
      • 4
        LRU eviction of keys
      • 3
        Data structure server
      • 3
        Performance & ease of use
      • 2
        Temporarily kept on disk
      • 2
        Dont save data if no subscribers are found
      • 2
        Automatic failover
      • 2
        Easy to use
      • 2
        Scalable
      • 2
        Channels concept
      • 2
        Object [key/value] size each 500 MB
      • 2
        Existing Laravel Integration
      • 2
        Simple
      CONS OF REDIS
      • 15
        Cannot query objects directly
      • 3
        No secondary indexes for non-numeric data types
      • 1
        No WAL

      related Redis posts

      Russel Werner
      Lead Engineer at StackShare · | 32 upvotes · 4.6M views

      StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

      Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

      #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

      See more
      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 12.7M 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
      Amazon S3 logo

      Amazon S3

      54K
      2K
      Store and retrieve any amount of data, at any time, from anywhere on the web
      54K
      2K
      PROS OF AMAZON S3
      • 590
        Reliable
      • 492
        Scalable
      • 456
        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
        Faster on response
      • 2
        Flexible
      • 2
        GDPR ready
      • 1
        Easy to use
      • 1
        Plug-gable
      • 1
        Easy integration with CloudFront
      CONS OF AMAZON S3
      • 7
        Permissions take some time to get right
      • 6
        Requires a credit card
      • 6
        Takes time/work to organize buckets & folders properly
      • 3
        Complex to set up

      related Amazon S3 posts

      Ashish Singh
      Tech Lead, Big Data Platform at Pinterest · | 38 upvotes · 3.7M 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
      Russel Werner
      Lead Engineer at StackShare · | 32 upvotes · 4.6M views

      StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

      Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

      #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

      See more