Need advice about which tool to choose?Ask the StackShare community!

Google App Engine

10K
7.8K
+ 1
610
Apache Tomcat

16.3K
12.2K
+ 1
201
Add tool

Apache Tomcat vs Google App Engine: What are the differences?

Introduction

Apache Tomcat and Google App Engine are both popular platforms used for developing and deploying web applications. While they have some similarities, there are several key differences between the two.

  1. Scalability: One of the main differences between Apache Tomcat and Google App Engine is the level of scalability they offer. Apache Tomcat allows for vertical scalability, where additional resources can be added to a single server to handle increased traffic. On the other hand, Google App Engine offers horizontal scalability, where multiple servers can be added to distribute the load and handle increasing traffic.

  2. Infrastructure Management: Apache Tomcat requires manual configuration and management of infrastructure, including server setup, software installation, and security configurations. In contrast, Google App Engine handles most of the infrastructure management tasks automatically, such as server provisioning, runtime environment, and server maintenance. This makes it easier for developers to focus on application development rather than infrastructure management.

  3. Vendor Lock-In: When using Apache Tomcat, developers have more freedom and flexibility as it is an open-source project. There is no vendor lock-in, and applications can be easily migrated or deployed to different hosting providers. On the other hand, Google App Engine is a proprietary platform offered by Google, which can create vendor lock-in. Migrating applications from Google App Engine to other platforms may require significant modifications and adjustments.

  4. Scale-to-Bill: Google App Engine provides a pay-per-use pricing model, where the platform automatically adjusts the resources allocated based on the application's needs. This allows for cost optimization and efficient resource utilization. In contrast, Apache Tomcat requires manual configuration and provisioning of resources, which may result in underutilized resources and higher costs.

  5. Data Storage: Apache Tomcat does not provide built-in data storage capabilities, and developers need to integrate third-party databases or file systems to handle data storage. On the other hand, Google App Engine provides a NoSQL database called Google Cloud Datastore, which offers scalable and robust data storage capabilities out of the box. This simplifies the development process and eliminates the need for additional database integration.

  6. Development Languages: Apache Tomcat supports multiple programming languages, including Java, PHP, Python, and more. Developers have the freedom to choose the language that best fits their application requirements. Google App Engine, on the other hand, provides native support for Java, Python, Node.js, Ruby, and Go. While it offers a wide range of supported languages, developers may have limited options compared to Apache Tomcat.

In summary, Apache Tomcat and Google App Engine differ in terms of scalability, infrastructure management, vendor lock-in, scale-to-bill pricing model, data storage capabilities, and supported development languages. These differences allow developers to choose the platform that best suits their application requirements and development preferences.

Decisions about Google App Engine and Apache Tomcat

I was in a situation where I have to configure 40 RHEL servers 20 each for Apache HTTP Server and Tomcat server. My task was to 1. configure LVM with required logical volumes, format and mount for HTTP and Tomcat servers accordingly. 2. Install apache and tomcat. 3. Generate and apply selfsigned certs to http server. 4. Modify default ports on Tomcat to different ports. 5. Create users on RHEL for application support team. 6. other administrative tasks like, start, stop and restart HTTP and Tomcat services.

I have utilized the power of ansible for all these tasks, which made it easy and manageable.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Google App Engine
Pros of Apache Tomcat
  • 145
    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
    Really easy to quickly bring up a full stack
  • 3
    Create APIs quickly with cloud endpoints
  • 2
    Mostly up
  • 2
    No Ops
  • 79
    Easy
  • 72
    Java
  • 49
    Popular
  • 1
    Spring web

Sign up to add or upvote prosMake informed product decisions

Cons of Google App Engine
Cons of Apache Tomcat
    Be the first to leave a con
    • 2
      Blocking - each http request block a thread
    • 1
      Easy to set up

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

    What is 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.

    What is Apache Tomcat?

    Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Google App Engine?
    What companies use Apache Tomcat?
    See which teams inside your own company are using Google App Engine or Apache Tomcat.
    Sign up for StackShare EnterpriseLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Google App Engine?
    What tools integrate with Apache Tomcat?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    What are some alternatives to Google App Engine and Apache Tomcat?
    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.
    DigitalOcean
    We take the complexities out of cloud hosting by offering blazing fast, on-demand SSD cloud servers, straightforward pricing, a simple API, and an easy-to-use control panel.
    AWS Lambda
    AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.
    Kubernetes
    Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
    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.
    See all alternatives