This document discusses Google App Engine (GAE) and how it can provide a scalable, reliable, and cost-effective platform for the National Research Institute for Earth Science and Disaster Prevention (NIED) in Japan to handle spikes in traffic during earthquakes. Some key components of GAE that help achieve this are its scalable and portable app design, non-relational Cloud Datastore, relational Cloud SQL, strong storage services, caching with Memcache, and developer assistance tools. Partnering with MiCloud could provide additional benefits like technical support, training, and hybrid cloud deployment options.

1. The Wonderful PaaS
GAE Introduction
MiCloud
Compute
Engine
Cloud
Storage
BigQuery
Cloud
Datastore
CloudSQL
App Engine

2. News...

3. Japan NIED earthquake

4. NIED Architecture

5. The Important things
● Scalability
○ as it gets spike of traffic at the event of earthquake
● Reliability
○ it's useless if it does not work at the time of disaster
● Cost efficiency
○ it's too expensive to prepare for enough hardware
resource that can handle the peak traffic. they would
be idle for the most of the time

6. The important components
What we don’t mentioned...
● Queue
Reverse Proxy /
System
AP Server
●
Load Balancer Cron Job
● Memcache
● Frontend Cache
● Version control
● Remote Backup
Developers
DBAs
Operators
Database / File
Server

7. Your Solution?

8. You NEED….
Google App Engine
It's not just a hosting service: App Engine empowers
you to design your app in the Googley way!

9. The Right Solution!
The Right Focus!

10. GAE Design Goal
- Significantly lower Total Cost of Ownership
●
●
●
●
Economy of scale
Easy to develop and deploy
Free to start - no initial cost
Lower operational cost
○ no security patches, upgrades, etc.
○ 24x7 operation by Google SREs

11. GAE Provides
● Portable and fine-grained app design
○
○
fast request handling to optimize server resource utilization
independent to each physical server
● Non-relational data model by Datastore/Bigtable
○
sharding, denormalization…
● RDBMS connect to Cloud SQL
○
auto backup, snapshot, global sync
● Strong storage service
○
global deploy, api access, bigquery integrate
● More fast temp store and cache
○
○
Memcache service
GAE frontend & static cache
● Developer Assistance
○ Cloud Management Console
○ Integrated development environment

12. GAE Architecture

13. GAE Future
●
●
●
●
Speed enhance
Global deployment - more zone support
More Google services integrate
More develop language support

14. Google Partner with MiCloud

15. MiCloud Advantage
● Technical Support
○ architecture design, service deployment…
● Training Support
○ technical training, skill transfer…
● Local IaaS Cloud provider
○ distributed deploy, efficient deploy, economy
deploy…
● S.I. experiences
○ more domain & local hook
○ more idea and innovation

16. Google - MiCloud Hybrid Cloud
Web Services
SQL Service
(GAE)
(Cloud SQL)
BigQuery
Support Ready
Dynamic
Resources
Google Cloud SQL Gateway (SSL)
Customized
Service with
Scale Support
AP Servers
AP Servers
(MiCloud DC1)
(MiCloud DC2)
HSM
Service

17. Q&A

18. Quota Management

19. Frontend cache benefits

20. Pending Latency & Idle Instance

21. How frontend cache do...

22. GAE Architecture (2009)

23. GAE Integration of Smart-Traveler

24. Google App Engine vs. JavaEE
Google App Engine:
●
●
●
●
●
Servlets 2.4, JSP 2.0
Partial support of JDO & JPA for the Datastore
JavaMail for... mail
JAXB
DOM, SAX, and XSLT for XML processing APIs
Java EE:
●
●
●
●
●
●
●
●
●
Enterprise Java Beans (EJB)
JAX-RPC
JAX-WS
Java Database Connectivity (JDBC)
Java EE™ Connector Architecture (JCA)
Java Management Extensions (JMX)
Java Message Service (JMS)
Java Naming and Directory Interface (JNDI)
Remote Method Invocation (RMI)