TrustRadius: an HG Insights company

CoreOS rkt / Container Linux (project ended) vs. Google App Engine

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    CoreOS rkt / Container Linux (project ended)

    Score8.5 out of 10
    N/ACoreOS rkt or Container Linux was a rival to Docker that was acquired by Red Hat, then given to the Cloud Native Computing Foundation (CNCF). The project has since been discontinued.N/A

    Google App Engine

    Score8.4 out of 10
    N/AGoogle App Engine is Google Cloud's platform-as-a-service offering. It features pay-per-use pricing and support for a broad array of programming languages.

    $0.05

    Per Hour Per Instance

    Pricing
    CoreOS rkt / Container Linux (project ended)Google App Engine
    Editions & Modules
    No answers on this topic
    Starting Price
    $0.05
    Per Hour Per Instance
    Max Price
    $0.30
    Per Hour Per Instance
    Offerings
    Pricing Offerings
    CoreOS rkt / Container Linux (project ended)Google App Engine
    Free Trial
    NoNo
    Free/Freemium Version
    NoYes
    Premium Consulting/Integration Services
    NoNo
    Entry-level Setup FeeNo setup feeNo setup fee
    Additional Details
    More Pricing Information
    Community Pulse
    CoreOS rkt / Container Linux (project ended)Google App Engine
    Considered Both Products
    Open Source
    Chose CoreOS rkt / Container Linux (project ended)
    We evaluated CoreOS rkt and Docker when selecting software solutions for my department. We ended up using CoreOS rkt because of how well it fits with CoreOS and the choice of gRPC for the API. We provide a managed service that runs CoreOS on a bare metal server, CoreOS rkt was …
    Incentivized
    Google
    No answer on this topic
    Key User Insights
    Would buy again
    No answers on this topic
    92%
    Would buy again
    12 Answers
    Delivers good value for the price
    No answers on this topic
    100%
    Delivers good value for the price
    13 Answers
    Happy with the feature set
    No answers on this topic
    92%
    Happy with the feature set
    12 Answers
    Lived up to sales and marketing promises
    No answers on this topic
    100%
    Lived up to sales and marketing promises
    10 Answers
    Implementation went as expected
    No answers on this topic
    92%
    Implementation went as expected
    12 Answers
    Features
    CoreOS rkt / Container Linux (project ended)Google App Engine
    Platform-as-a-Service
    Comparison of Platform-as-a-Service features of CoreOS rkt / Container Linux (project ended) and Google App Engine
    Feature
    CoreOS rkt / Container Linux (project ended)
    -
    Ratings
    Google App Engine
    9.5
    32 Ratings
    20% above category average
    Ease of building user interfaces00 Ratings9.018 Ratings
    Scalability00 Ratings10.032 Ratings
    Platform management overhead00 Ratings9.032 Ratings
    Workflow engine capability00 Ratings8.024 Ratings
    Platform access control00 Ratings10.031 Ratings
    Services-enabled integration00 Ratings10.028 Ratings
    Development environment creation00 Ratings10.029 Ratings
    Development environment replication00 Ratings10.028 Ratings
    Issue monitoring and notification00 Ratings9.028 Ratings
    Issue recovery00 Ratings9.026 Ratings
    Upgrades and platform fixes00 Ratings10.029 Ratings
    Best Alternatives
    CoreOS rkt / Container Linux (project ended)Google App Engine
    Small Businesses
    Mirantis Kubernetes Engine
    Score8 out of 10
    IBM Cloud Foundry
    Score8.5 out of 10
    Medium-sized Companies
    Amazon Elastic Container Service (Amazon ECS)
    Score8.6 out of 10
    IBM Cloud Private
    Score9.6 out of 10
    Enterprises
    SUSE Rancher
    Score9.3 out of 10
    AWS Elastic Beanstalk
    Score8.6 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    CoreOS rkt / Container Linux (project ended)Google App Engine
    Likelihood to Recommend
    7.0
    (2 ratings)
    9.0
    (36 ratings)
    Likelihood to Renew
    -
    (0 ratings)
    8.3
    (8 ratings)
    Usability
    -
    (0 ratings)
    10.0
    (8 ratings)
    Performance
    -
    (0 ratings)
    10.0
    (1 ratings)
    Support Rating
    -
    (0 ratings)
    8.4
    (12 ratings)
    Implementation Rating
    -
    (0 ratings)
    8.0
    (1 ratings)
    User Testimonials
    CoreOS rkt / Container Linux (project ended)Google App Engine
    Likelihood to Recommend
    Open Source
    CoreOS rkt is well suited for any development environment where operating systems and hardware are not homogeneous. CoreOS rkt allows us to write code on one machine with the confidence that it will work on any other. This has been immensely helpful as our developers are often switching to the latest and greatest machines and operating systems. CoreOS rkt is less suited for environments that are not Software as a Service. There is often no need to bring the entire developer environment and associated dependencies when delivering a one time product. In these environments CoreOS rkt just adds unneeded overhead.
    Incentivized
    Read full review
    Google
    App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.
    Incentivized
    Read full review
    Pros
    Open Source
    • Running a secure container without messing up with low-level details
    • Very clear and straightforward approach to building a container
    • A way to go for new projects thinking of containers
    • Comprehensive and well-written documentation compatible with UNIX keep it simple way of thinking
    Incentivized
    Read full review
    Google
    • Quick to develop, quick to deploy. You can be up and running on Google App Engine in no time.
    • Flexible. We use Java for some services and Node.js for others.
    • Great security features. We have been consistently impressed with the security and authentication features of Google App Engine.
    Incentivized
    Read full review
    Cons
    Open Source
    • Market share, it's often very difficult to find new talent who use CoreOS rkt.
    • Lack of wow features, CoreOS rkt doesn't necessarily offer any immediate advantages over other container solutions.
    Incentivized
    Read full review
    Google
    • There is a slight learning curve to getting used to code on Google App Engine.
    • Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
    • Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)
    Incentivized
    Read full review
    Likelihood to Renew
    Open Source
    No answers on this topic
    Google
    App Engine is a solid choice for deployments to Google Cloud Platform that do not want to move entirely to a Kubernetes-based container architecture using a different Google product. For rapid prototyping of new applications and fairly straightforward web application deployments, we'll continue to leverage the capabilities that App Engine affords us.
    Incentivized
    Read full review
    Usability
    Open Source
    No answers on this topic
    Google
    I had to revisit the UI after a year of just setting up and forgetting. The UI got some improvements but the amount of navigation we have to go through to setup a new app has increased but also got easier to setup. Gemini now is integrated and make getting answers faster
    Incentivized
    Read full review
    Support Rating
    Open Source
    No answers on this topic
    Google
    Good amount of documentation available for Google App Engine and in general there is large developer community around Google App Engine and other products it interacts with. Lastly, Google support is great in general. No issues so far with them.
    Incentivized
    Read full review
    Alternatives Considered
    Open Source
    Docker, lxc, Ubuntu Snappy, partisan chroot+unshare Reformulating the problem and realizing a container is not necessary when a testing environment with clearly defined behavior.
    Incentivized
    Read full review
    Google
    We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as compared to the other major players in Azure and AWS.
    Incentivized
    Read full review
    Return on Investment
    Open Source
    • Developers spend less time configuring and more time coding.
    • Less time training developers as CoreOS rkt lets them use whatever hardware and operating system they want.
    • Reduced our IT costs, solutions are containerized using CoreOS rkt meaning they can write one solution with many developers in mind.
    Incentivized
    Read full review
    Google
    • Effective employee adoption through ease of use.
    • Effective integration to other java based frameworks.
    • Time to market is very quick. Build, test, deploy and use.
    • The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.
    Incentivized
    Read full review
    ScreenShots