Alternatives to Cloud 66 logo

Alternatives to Cloud 66

Heroku, Codeship, Google App Engine, Apollo, and AWS Elastic Beanstalk are the most popular alternatives and competitors to Cloud 66.
35
33
+ 1
90

What is Cloud 66 and what are its top alternatives?

Cloud 66 gives you everything you need to build, deploy and maintain your applications on any cloud, without the headache of dealing with "server stuff". Frameworks: Ruby on Rails, Node.js, Jamstack, Laravel, GoLang, and more.
Cloud 66 is a tool in the Platform as a Service category of a tech stack.

Top Alternatives to Cloud 66

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

  • Codeship
    Codeship

    Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need. ...

  • Google App Engine
    Google App Engine

    Google has a reputation for highly reliable, high performance infrastructure. With App Engine you can take advantage of the 10 years of knowledge Google has in running massively scalable, performance driven systems. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow. ...

  • Apollo
    Apollo

    Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes. ...

  • AWS Elastic Beanstalk
    AWS Elastic Beanstalk

    Once you upload your application, Elastic Beanstalk automatically handles the deployment details of capacity provisioning, load balancing, auto-scaling, and application health monitoring. ...

  • Apache Camel
    Apache Camel

    An open source Java framework that focuses on making integration easier and more accessible to developers. ...

  • Red Hat OpenShift
    Red Hat OpenShift

    OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications. ...

  • AWS CodePipeline
    AWS CodePipeline

    CodePipeline builds, tests, and deploys your code every time there is a code change, based on the release process models you define. ...

Cloud 66 alternatives & related posts

Heroku logo

Heroku

22.6K
18K
3.2K
Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
22.6K
18K
+ 1
3.2K
PROS OF HEROKU
  • 704
    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
  • 24
    Super expensive
  • 7
    Not a whole lot of flexibility
  • 5
    No usable MySQL option
  • 5
    Storage
  • 4
    Low performance on free tier
  • 1
    24/7 support is $1,000 per month

related Heroku posts

Russel Werner
Lead Engineer at StackShare · | 32 upvotes · 1.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 · | 29 upvotes · 4.6M 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
Codeship logo

Codeship

1K
733
1.5K
A Continuous Integration Platform in the cloud
1K
733
+ 1
1.5K
PROS OF CODESHIP
  • 215
    Simple deployments
  • 179
    Easy setup
  • 159
    Github integration
  • 147
    Continuous deployment
  • 110
    Bitbucket integration
  • 97
    Easy ui
  • 84
    Slack integration
  • 66
    Fast builds
  • 61
    Great ui
  • 61
    Great customer support
  • 28
    SSH debug access
  • 27
    Free plan for 5 private repositories
  • 27
    Easy to get started
  • 23
    Competitively priced
  • 20
    Notifications
  • 20
    Hipchat, Campfire integrations
  • 16
    Awesome UI
  • 15
    Fast
  • 14
    Great documentation
  • 13
    Great experience
  • 12
    Free for open source
  • 10
    Great Tutorials
  • 4
    GitLab integration
  • 4
    Free
  • 4
    Easy to use, above all and its free for basic use
  • 3
    Easy for CI first timers
  • 3
    BitBucket Support
  • 3
    Very easy to get started
  • 3
    Build private Github repos on the free plan
  • 3
    Awesome
  • 2
    Super easy setup, works great with py.test/tox
  • 2
    Openshift integration
  • 2
    Great support, even on free tier
  • 2
    AppEngine integration
  • 2
    Easy debugging with ssh
  • 2
    Integrates with other free software
  • 2
    Superfast team work integration
  • 2
    Grepping Codeship = 1 day. Grepping Bamboo = 1 month
  • 2
    Easy to set up, very nice GitHub integration
  • 2
    Up and running in few minutes, and above all UI
CONS OF CODESHIP
  • 3
    Ui could use some polishing
  • 0
    Antiquated ui
  • 0
    Difficult to answer build questions

related Codeship posts

Sebastian Dellwig
Tech Lead at Porsche Digital GmbH · | 6 upvotes · 160.6K views
Shared insights
on
GitLab CIGitLab CICircleCICircleCICodeshipCodeship

We are using GitLab CI and were very happy with it. The integration of all tools like CI/CD, tickets, etc makes it very easy to stay on top of things. But be aware, Gitlab currently does not have iOS build support. So if you want to exchange that for CircleCI / Codeship to have to invest some effort. We are using a managed Mac OS device and installed the Gitlab runner there, to have iOS builds.

See more
Google App Engine logo

Google App Engine

8.5K
6.7K
609
Build web applications on the same scalable systems that power Google applications
8.5K
6.7K
+ 1
609
PROS OF GOOGLE APP ENGINE
  • 144
    Easy to deploy
  • 106
    Auto scaling
  • 80
    Good free plan
  • 62
    Easy management
  • 56
    Scalability
  • 35
    Low cost
  • 32
    Comprehensive set of features
  • 28
    All services in one place
  • 22
    Simple scaling
  • 19
    Quick and reliable cloud servers
  • 6
    Granular Billing
  • 5
    Easy to develop and unit test
  • 4
    Monitoring gives comprehensive set of key indicators
  • 3
    Create APIs quickly with cloud endpoints
  • 3
    Really easy to quickly bring up a full stack
  • 2
    No Ops
  • 2
    Mostly up
CONS OF GOOGLE APP ENGINE
    Be the first to leave a con

    related Google App Engine posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 11 upvotes · 328.1K views

    So, the shift from Amazon EC2 to Google App Engine and generally #AWS to #GCP was a long decision and in the end, it's one that we've taken with eyes open and that we reserve the right to modify at any time. And to be clear, we continue to do a lot of stuff with AWS. But, by default, the content of the decision was, for our consumer-facing products, we're going to use GCP first. And if there's some reason why we don't think that's going to work out great, then we'll happily use AWS. In practice, that hasn't really happened. We've been able to meet almost 100% of our needs in GCP.

    So it's basically mostly Google Kubernetes Engine , we're mostly running stuff on Kubernetes right now.

    #AWStoGCPmigration #cloudmigration #migration

    See more
    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
    Apollo logo

    Apollo

    2.1K
    1.6K
    22
    GraphQL server for Express, Connect, Hapi, Koa and more
    2.1K
    1.6K
    + 1
    22
    PROS OF APOLLO
    • 12
      From the creators of Meteor
    • 5
      Great documentation
    • 3
      Open source
    • 2
      Real time if use subscription
    CONS OF APOLLO
    • 1
      File upload is not supported
    • 1
      Increase in complexity of implementing (subscription)

    related Apollo posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 44 upvotes · 2.1M 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
    Adam Neary

    At Airbnb we use GraphQL Unions for a "Backend-Driven UI." We have built a system where a very dynamic page is constructed based on a query that will return an array of some set of possible “sections.” These sections are responsive and define the UI completely.

    The central file that manages this would be a generated file. Since the list of possible sections is quite large (~50 sections today for Search), it also presumes we have a sane mechanism for lazy-loading components with server rendering, which is a topic for another post. Suffice it to say, we do not need to package all possible sections in a massive bundle to account for everything up front.

    Each section component defines its own query fragment, colocated with the section’s component code. This is the general idea of Backend-Driven UI at Airbnb. It’s used in a number of places, including Search, Trip Planner, Host tools, and various landing pages. We use this as our starting point, and then in the demo show how to (1) make and update to an existing section, and (2) add a new section.

    While building your product, you want to be able to explore your schema, discovering field names and testing out potential queries on live development data. We achieve that today with GraphQL Playground, the work of our friends at #Prisma. The tools come standard with Apollo Server.

    #BackendDrivenUI

    See more
    AWS Elastic Beanstalk logo

    AWS Elastic Beanstalk

    2.1K
    1.7K
    240
    Quickly deploy and manage applications in the AWS cloud.
    2.1K
    1.7K
    + 1
    240
    PROS OF AWS ELASTIC BEANSTALK
    • 77
      Integrates with other aws services
    • 65
      Simple deployment
    • 44
      Fast
    • 28
      Painless
    • 16
      Free
    • 3
      Independend app container
    • 3
      Well-documented
    • 2
      Postgres hosting
    • 2
      Ability to be customized
    CONS OF AWS ELASTIC BEANSTALK
    • 2
      Charges appear automatically after exceeding free quota
    • 1
      Lots of moving parts and config
    • 0
      Slow deployments

    related AWS Elastic Beanstalk posts

    Julien DeFrance
    Principal Software Engineer at Tophatter · | 16 upvotes · 2.5M 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

    We initially started out with Heroku as our PaaS provider due to a desire to use it by our original developer for our Ruby on Rails application/website at the time. We were finding response times slow, it was painfully slow, sometimes taking 10 seconds to start loading the main page. Moving up to the next "compute" level was going to be very expensive.

    We moved our site over to AWS Elastic Beanstalk , not only did response times on the site practically become instant, our cloud bill for the application was cut in half.

    In database world we are currently using Amazon RDS for PostgreSQL also, we have both MariaDB and Microsoft SQL Server both hosted on Amazon RDS. The plan is to migrate to AWS Aurora Serverless for all 3 of those database systems.

    Additional services we use for our public applications: AWS Lambda, Python, Redis, Memcached, AWS Elastic Load Balancing (ELB), Amazon Elasticsearch Service, Amazon ElastiCache

    See more
    Apache Camel logo

    Apache Camel

    1.5K
    266
    22
    A versatile open source integration framework
    1.5K
    266
    + 1
    22
    PROS OF APACHE CAMEL
    • 5
      Based on Enterprise Integration Patterns
    • 4
      Has over 250 components
    • 4
      Free (open source)
    • 4
      Highly configurable
    • 3
      Open Source
    • 2
      Has great community
    CONS OF APACHE CAMEL
      Be the first to leave a con

      related Apache Camel posts

      Red Hat OpenShift logo

      Red Hat OpenShift

      1.3K
      1.3K
      500
      Red Hat's free Platform as a Service (PaaS) for hosting Java, PHP, Ruby, Python, Node.js, and Perl apps
      1.3K
      1.3K
      + 1
      500
      PROS OF RED HAT OPENSHIFT
      • 98
        Good free plan
      • 62
        Open Source
      • 46
        Easy setup
      • 42
        Nodejs support
      • 41
        Well documented
      • 32
        Custom domains
      • 28
        Mongodb support
      • 27
        Clean and simple architecture
      • 25
        PHP support
      • 21
        Customizable environments
      • 11
        Ability to run CRON jobs
      • 9
        Easier than Heroku for a WordPress blog
      • 7
        Autoscaling
      • 7
        Easy deployment
      • 7
        Good balance between Heroku and AWS for flexibility
      • 6
        PostgreSQL support
      • 5
        Free, Easy Setup, Lot of Gear or D.I.Y Gear
      • 4
        Shell access to gears
      • 3
        Great Support
      • 2
        Meteor support
      • 2
        Overly complicated and over engineered in majority of e
      • 2
        High Security
      • 2
        Its free and offer custom domain usage
      • 2
        Golang support
      • 1
        No credit card needed
      • 1
        Runs Anywhere - AWS, GCP, Azure
      • 1
        Secure
      • 1
        Logging & Metrics
      • 1
        This is the only free one among the three as of today
      • 1
        Great free plan with excellent support
      • 1
        because it is easy to manage
      • 1
        Autoscaling at a good price point
      • 1
        Easy setup and great customer support
      CONS OF RED HAT OPENSHIFT
      • 2
        Decisions are made for you, limiting your options
      • 2
        License cost
      • 1
        Behind, sometimes severely, the upstreams

      related Red Hat OpenShift posts

      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.2M views

      How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

      Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

      Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

      https://eng.uber.com/distributed-tracing/

      (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

      Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

      See more
      Michael Ionita

      We use Kubernetes because we decided to migrate to a hosted cluster (not AWS) and still be able to scale our clusters up and down depending on load. By wrapping it with OpenShift we are now able to easily adapt to demand but also able to separate concerns into separate Pods depending on use-cases we have.

      See more
      AWS CodePipeline logo

      AWS CodePipeline

      514
      810
      30
      Continuous delivery service for fast and reliable application updates
      514
      810
      + 1
      30
      PROS OF AWS CODEPIPELINE
      • 13
        Simple to set up
      • 8
        Managed service
      • 4
        GitHub integration
      • 3
        Parallel Execution
      • 2
        Automatic deployment
      • 0
        Manual Steps Available
      CONS OF AWS CODEPIPELINE
      • 2
        No project boards
      • 1
        No integration with "Power" 365 tools

      related AWS CodePipeline posts

      Khauth György
      CTO at SalesAutopilot Kft. · | 12 upvotes · 479.1K views

      I'm the CTO of a marketing automation SaaS. Because of the continuously increasing load we moved to the AWSCloud. We are using more and more features of AWS: Amazon CloudWatch, Amazon SNS, Amazon CloudFront, Amazon Route 53 and so on.

      Our main Database is MySQL but for the hundreds of GB document data we use MongoDB more and more. We started to use Redis for cache and other time sensitive operations.

      On the front-end we use jQuery UI + Smarty but now we refactor our app to use Vue.js with Vuetify. Because our app is relatively complex we need to use vuex as well.

      On the development side we use GitHub as our main repo, Docker for local and server environment and Jenkins and AWS CodePipeline for Continuous Integration.

      See more
      Oliver Burn
      Architect at Atlassian · | 12 upvotes · 379K views

      We recently added new APIs to Jira to associate information about Builds and Deployments to Jira issues.

      The new APIs were developed using a spec-first API approach for speed and sanity. The details of this approach are described in this blog post, and we relied on using Swagger and associated tools like Swagger UI.

      A new service was created for managing the data. It provides a REST API for external use, and an internal API based on GraphQL. The service is built using Kotlin for increased developer productivity and happiness, and the Spring-Boot framework. PostgreSQL was chosen for the persistence layer, as we have non-trivial requirements that cannot be easily implemented on top of a key-value store.

      The front-end has been built using React and querying the back-end service using an internal GraphQL API. We have plans of providing a public GraphQL API in the future.

      New Jira Integrations: Bitbucket CircleCI AWS CodePipeline Octopus Deploy jFrog Azure Pipelines

      See more