Alternatives to Elastic Cloud logo

Alternatives to Elastic Cloud

logz.io, Cloud Foundry, Amazon EC2, Algolia, and Amazon Elasticsearch Service are the most popular alternatives and competitors to Elastic Cloud.
61
71
+ 1
0

What is Elastic Cloud and what are its top alternatives?

A growing family of Elastic SaaS offerings that make it easy to deploy, operate, and scale Elastic products and solutions in the cloud. From an easy-to-use hosted and managed Elasticsearch experience to powerful, out-of-the-box search solutions.
Elastic Cloud is a tool in the Platform as a Service category of a tech stack.

Top Alternatives to Elastic Cloud

  • logz.io
    logz.io

    It provides Elasticsearch, Logstash and Kibana on the cloud with alerts, unlimited scalability and free ELK apps. Index, search & visualize your data. ...

  • Cloud Foundry
    Cloud Foundry

    Cloud Foundry is an open platform as a service (PaaS) that provides a choice of clouds, developer frameworks, and application services. Cloud Foundry makes it faster and easier to build, test, deploy, and scale applications. ...

  • Amazon EC2
    Amazon EC2

    It is a web service that provides resizable compute capacity in the cloud. It is designed to make web-scale computing easier for developers. ...

  • Algolia
    Algolia

    Our mission is to make you a search expert. Push data to our API to make it searchable in real time. Build your dream front end with one of our web or mobile UI libraries. Tune relevance and get analytics right from your dashboard. ...

  • Amazon Elasticsearch Service
    Amazon Elasticsearch Service

    Amazon Elasticsearch Service is a fully managed service that makes it easy for you to deploy, secure, and operate Elasticsearch at scale with zero down time. ...

  • Elasticsearch
    Elasticsearch

    Elasticsearch is a distributed, RESTful search and analytics engine capable of storing data and searching it in near real time. Elasticsearch, Kibana, Beats and Logstash are the Elastic Stack (sometimes called the ELK Stack). ...

  • Splunk
    Splunk

    It provides the leading platform for Operational Intelligence. Customers use it to search, monitor, analyze and visualize machine data. ...

  • Heroku
    Heroku

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling. ...

Elastic Cloud alternatives & related posts

logz.io logo

logz.io

57
50
0
A log management and log analysis service
57
50
+ 1
0
PROS OF LOGZ.IO
    Be the first to leave a pro
    CONS OF LOGZ.IO
      Be the first to leave a con

      related logz.io posts

      Cloud Foundry logo

      Cloud Foundry

      190
      344
      5
      Deploy and scale applications in seconds on your choice of private or public cloud
      190
      344
      + 1
      5
      PROS OF CLOUD FOUNDRY
      • 2
        Perfectly aligned with springboot
      • 1
        Free distributed tracing (zipkin)
      • 1
        Application health management
      • 1
        Free service discovery (Eureka)
      CONS OF CLOUD FOUNDRY
        Be the first to leave a con

        related Cloud Foundry posts

        Amazon EC2 logo

        Amazon EC2

        47.8K
        35.1K
        2.5K
        Scalable, pay-as-you-go compute capacity in the cloud
        47.8K
        35.1K
        + 1
        2.5K
        PROS OF AMAZON EC2
        • 647
          Quick and reliable cloud servers
        • 515
          Scalability
        • 393
          Easy management
        • 277
          Low cost
        • 271
          Auto-scaling
        • 89
          Market leader
        • 80
          Backed by amazon
        • 79
          Reliable
        • 67
          Free tier
        • 58
          Easy management, scalability
        • 13
          Flexible
        • 10
          Easy to Start
        • 9
          Elastic
        • 9
          Web-scale
        • 9
          Widely used
        • 7
          Node.js API
        • 5
          Industry Standard
        • 4
          Lots of configuration options
        • 2
          GPU instances
        • 1
          Simpler to understand and learn
        • 1
          Extremely simple to use
        • 1
          Amazing for individuals
        • 1
          All the Open Source CLI tools you could want.
        CONS OF AMAZON EC2
        • 13
          Ui could use a lot of work
        • 6
          High learning curve when compared to PaaS
        • 3
          Extremely poor CPU performance

        related Amazon EC2 posts

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

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

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

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

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

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

        #BigData #AWS #DataScience #DataEngineering

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

        Algolia

        1.4K
        1.1K
        697
        Developer-friendly API and complete set of tools for building search
        1.4K
        1.1K
        + 1
        697
        PROS OF ALGOLIA
        • 126
          Ultra fast
        • 95
          Super easy to implement
        • 73
          Modern search engine
        • 71
          Excellent support
        • 70
          Easy setup, fast and relevant
        • 46
          Typos handling
        • 40
          Search analytics
        • 31
          Designed to search records, not pages
        • 30
          Distributed Search Network
        • 30
          Multiple datacenters
        • 10
          Smart Highlighting
        • 9
          Search as you type
        • 8
          Multi-attributes
        • 8
          Instantsearch.js
        • 6
          Super fast, easy to set up
        • 5
          Database search
        • 5
          Amazing uptime
        • 4
          Realtime
        • 4
          Github-awesome-autocomple
        • 4
          Great documentation
        • 4
          Highly customizable
        • 3
          Beautiful UI
        • 3
          Powerful Search
        • 3
          Places.js
        • 2
          Awesome aanltiycs and typos hnadling
        • 2
          Integrates with just about everything
        • 1
          Developer-friendly frontend libraries
        • 1
          Ok to use
        • 1
          Fast response time
        • 1
          Github integration
        • 1
          Smooth platform
        • 0
          Fuck
        • 0
          Giitera
        • 0
          Is it fool
        • 0
          Nooo
        CONS OF ALGOLIA
        • 11
          Expensive

        related Algolia posts

        Julien DeFrance
        Principal Software Engineer at Tophatter · | 16 upvotes · 3.1M 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 · | 16 upvotes · 504.2K views

        Although we were using Elasticsearch in the beginning to power our in-app search, we moved this part of our processing over to Algolia a couple of months ago; this has proven to be a fantastic choice, letting us build search-related features with more confidence and speed.

        Elasticsearch is only used for searching in internal tooling nowadays; hosting and running it reliably has been a task that took up too much time for us in the past and fine-tuning the results to reach a great user-experience was also never an easy task for us. With Algolia we can flexibly change ranking methods on the fly and can instead focus our time on fine-tuning the experience within our app.

        Memcached is used in front of most of the API endpoints to cache responses in order to speed up response times and reduce server-costs on our side.

        #SearchAsAService

        See more
        Amazon Elasticsearch Service logo

        Amazon Elasticsearch Service

        381
        286
        24
        Real-time, distributed search and analytics engine that fits nicely into a cloud environment
        381
        286
        + 1
        24
        PROS OF AMAZON ELASTICSEARCH SERVICE
        • 10
          Easy setup, monitoring and scaling
        • 7
          Kibana
        • 7
          Document-oriented
        CONS OF AMAZON ELASTICSEARCH SERVICE
          Be the first to leave a con

          related Amazon Elasticsearch Service posts

          Julien DeFrance
          Principal Software Engineer at Tophatter · | 16 upvotes · 3.1M 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
          Chris McFadden
          VP, Engineering at SparkPost · | 9 upvotes · 468.2K views

          We send over 20 billion emails a month on behalf of our customers. As a result, we manage hundreds of millions of "suppression" records that track when an email address is invalid as well as when a user unsubscribes or flags an email as spam. This way we can help ensure our customers are only sending email that their recipients want, which boosts overall delivery rates and engagement. We need to support two primary use cases: (1) fast and reliable real-time lookup against the list when sending email and (2) allow customers to search, edit, and bulk upload/download their list via API and in the UI. A single enterprise customer's list can be well over 100 million. Over the years as the size of this data started small and has grown increasingly we have tried multiple things that didn't scale very well. In the recent past we used Amazon DynamoDB for the system of record as well as a cache in Amazon ElastiCache (Redis) for the fast lookups and Amazon CloudSearch for the search function. This architecture was overly complicated and expensive. We were able to eliminate the use of Redis, replacing it with direct lookups against DynamoDB, fronted with a stripped down Node.js API that performs consistently around 10ms. The new dynamic bursting of DynamoDB has helped ensure reliable and consistent performance for real-time lookups. We also moved off the clunky and expensive CloudSearch to Amazon Elasticsearch Service for the search functionality. Beyond the high price tag for CloudSearch it also had severe limits streaming updates from DynamoDB, which forced us to batch them - adding extra complexity and CX challenges. We love the fact that DynamoDB can stream directly to ElasticSearch and believe using these two technologies together will handle our scaling needs in an economical way for the foreseeable future.

          See more
          Elasticsearch logo

          Elasticsearch

          34.7K
          26.4K
          1.6K
          Open Source, Distributed, RESTful Search Engine
          34.7K
          26.4K
          + 1
          1.6K
          PROS OF ELASTICSEARCH
          • 326
            Powerful api
          • 315
            Great search engine
          • 230
            Open source
          • 214
            Restful
          • 199
            Near real-time search
          • 97
            Free
          • 84
            Search everything
          • 54
            Easy to get started
          • 45
            Analytics
          • 26
            Distributed
          • 6
            Fast search
          • 5
            More than a search engine
          • 3
            Highly Available
          • 3
            Awesome, great tool
          • 3
            Great docs
          • 3
            Easy to scale
          • 2
            Fast
          • 2
            Easy setup
          • 2
            Great customer support
          • 2
            Intuitive API
          • 2
            Great piece of software
          • 2
            Reliable
          • 2
            Potato
          • 2
            Nosql DB
          • 2
            Document Store
          • 1
            Not stable
          • 1
            Scalability
          • 1
            Open
          • 1
            Github
          • 1
            Elaticsearch
          • 1
            Actively developing
          • 1
            Responsive maintainers on GitHub
          • 1
            Ecosystem
          • 1
            Easy to get hot data
          • 0
            Community
          CONS OF ELASTICSEARCH
          • 7
            Resource hungry
          • 6
            Diffecult to get started
          • 5
            Expensive
          • 4
            Hard to keep stable at large scale

          related Elasticsearch posts

          Tim Abbott

          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
          Tymoteusz Paul
          Devops guy at X20X Development LTD · | 23 upvotes · 8M views

          Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

          It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

          I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

          We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

          If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

          The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

          Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

          See more
          Splunk logo

          Splunk

          753
          993
          20
          Search, monitor, analyze and visualize machine data
          753
          993
          + 1
          20
          PROS OF SPLUNK
          • 3
            API for searching logs, running reports
          • 3
            Alert system based on custom query results
          • 2
            Dashboarding on any log contents
          • 2
            Custom log parsing as well as automatic parsing
          • 2
            Ability to style search results into reports
          • 2
            Query engine supports joining, aggregation, stats, etc
          • 2
            Splunk language supports string, date manip, math, etc
          • 2
            Rich GUI for searching live logs
          • 1
            Query any log as key-value pairs
          • 1
            Granular scheduling and time window support
          CONS OF SPLUNK
          • 1
            Splunk query language rich so lots to learn

          related Splunk posts

          Shared insights
          on
          KibanaKibanaSplunkSplunkGrafanaGrafana

          I use Kibana because it ships with the ELK stack. I don't find it as powerful as Splunk however it is light years above grepping through log files. We previously used Grafana but found it to be annoying to maintain a separate tool outside of the ELK stack. We were able to get everything we needed from Kibana.

          See more
          Shared insights
          on
          SplunkSplunkElasticsearchElasticsearch

          We are currently exploring Elasticsearch and Splunk for our centralized logging solution. I need some feedback about these two tools. We expect our logs in the range of upwards > of 10TB of logging data.

          See more
          Heroku logo

          Heroku

          25.4K
          20.1K
          3.2K
          Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
          25.4K
          20.1K
          + 1
          3.2K
          PROS OF HEROKU
          • 703
            Easy deployment
          • 459
            Free for side projects
          • 374
            Huge time-saver
          • 348
            Simple scaling
          • 261
            Low devops skills required
          • 190
            Easy setup
          • 174
            Add-ons for almost everything
          • 153
            Beginner friendly
          • 150
            Better for startups
          • 133
            Low learning curve
          • 48
            Postgres hosting
          • 41
            Easy to add collaborators
          • 30
            Faster development
          • 24
            Awesome documentation
          • 19
            Simple rollback
          • 19
            Focus on product, not deployment
          • 15
            Natural companion for rails development
          • 15
            Easy integration
          • 12
            Great customer support
          • 8
            GitHub integration
          • 6
            Painless & well documented
          • 6
            No-ops
          • 4
            I love that they make it free to launch a side project
          • 4
            Free
          • 3
            Great UI
          • 3
            Just works
          • 2
            PostgreSQL forking and following
          • 2
            MySQL extension
          • 1
            Security
          • 1
            Able to host stuff good like Discord Bot
          • 0
            Sec
          CONS OF HEROKU
          • 27
            Super expensive
          • 9
            Not a whole lot of flexibility
          • 7
            No usable MySQL option
          • 7
            Storage
          • 5
            Low performance on free tier
          • 2
            24/7 support is $1,000 per month

          related Heroku posts

          Russel Werner
          Lead Engineer at StackShare · | 32 upvotes · 1.9M 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 · 8.9M 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