Download as PDF, PPTX
Uploaded byVirtual JBoss User Group
Implementing your own Google App Engine
The document outlines the integration of Google App Engine applications into the WildFly environment using the Capedwarf framework, emphasizing ease of setup, scalability, and elimination of vendor lock-in. Capedwarf operates as an open-source implementation of the Google App Engine API, enabling developers to run and manage their applications locally or in a cloud environment. Key highlights include testing tools, management capabilities, and a comprehensive feature set that supports multitenancy and various API functionalities.
More Related Content
Similar to Implementing your own Google App Engine
Implementing your own Google App Engine
- 1. Implementing your own GoogleApp Engine Aleš Justin, Red Hat
- 2. The goal • Takean *existing* Google App Engine app • Drop it into WildFly • It just works! • No vendor lock-in • Enable cluster debugging / testing • On-premises cloud! • Designed to scale
- 3. • What’s GoogleApp Engine? • What is JBoss CapeDwarf? • How do the two work together? • The dirty details • Demo • Q&A Agenda
- 4. • Aleš Justin •CapeDwarf Project Founder & Lead • Old School JBoss-ian; MC, CDI, Ceylon, ... Who’s this guy?
- 5. “Google App Enginelets you run web applications on Google's infrastructure. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow. With App Engine, there are no servers to maintain: You just upload your application, and it's ready to serve your users.” It’s all about services and its API! What is Google App Engine?
- 6. • Open sourceimplementation of Google App Engine API • It’s all about the API, not impl - for users • Written on top of JBoss and other OS frameworks • Infinispan, Hibernate Search, HornetQ, Lucene, ... • Runs as a WildFly subsystem / extension • Management, Clustering, ... What is CapeDwarf?
- 7. • Super easyto setup locally - unzip & run • Same way as any WildFly / JBossAS • Trivial to setup cluster • A way to debug scalable apps • Integrated into OpenShift (Red Hat PaaS) • Own CapeDwarf cartridge / image • On-premises cloud env What is CapeDwarf?
- 8. • 100% pureJava • It’s all on GitHub • https://github.com/capedwarf What is CapeDwarf?
- 9. AppIdentity ✔ Multitenancy✿ Blobstore ✔ OAuth ✔ Capabilities ✿ (Prospective)Search ✔ Channel ✔ Tasks ✔ Datastore ✔ URLFetch ✔ Files / GCS ✔ Users ✔ Images ✔ XMPP ✿ Logging ✔ Admin Console ✿ Mail ✿ JPA / JDO ✔ Memcache ✔ MapReduce ✔ Cron ✔ Warm-up ✔ Modules ✔ Endpoints ✔ Sockets ✔ SQL ✔ Current API matrix
- 10. ... or howdo we know CapeDwarf actually works ... More about this in next slides :-) Testing?
- 11. • Google AppEngine Technology Compatibility Kit (TCK) • Joint (initial) effort from Google and Red Hat • http://www.appengine-tck.org • 1000+ API tests • Additional testing - Endpoints, DataNucleus, MapReduce, Modules, Concurrency, … • GCloud support (aka Managed / Custom Runtimes) Google App Engine & CapeDwarf
- 12. • Runs withMaven • JUnit,Arquillian and ShrinkWrap based • Nice API test coverage report • Easy to add new containers / runtimes • Using GitHub’ “community” power; pull-request, review, ... About TCK
- 13. Switch screen! TCK coveragereport view
- 14. • Simply createnew TCK test • Plain JUnit @Test • @RunWith(Arquillian.class) • New ShrinkWrap @Deployment • GitHub Pull-Request Bugs?
- 15. • Few impldetails • Datastore → Infinispan & Co. • TaskQueue → JMS / HornetQ • Endpoints → Tweaking Endpoints code • Modules • Runtime → WildFly • Subsystem → Deployers, Services, ... How does CapeDwarf work?
- 16. Datastore Datastore InfinispanQuery Search LuceneFSClustering Datastore Datastore
- 17. App AppApp Async task JMS Invocation TxBalancing Queue
- 18. • Standalone • Properlymap JEE .ear onto GAE Modules logic • Setup virtual-servers for each module • Domain (TODO) • Custom DomainController • Each module gets own app server instance • Could share app servers • Testing → new Arquillian Protocol Modules
- 19. • Extending WildFly→ New Subsystem • It’s all about DeploymentUnitProcessors • Remember JBoss Deployers? ;-) • 10+ DUPs, per phase / purpose • Almost zero configuration • Few MSC services • Fully modular • in-line API jar or as-module CapeDwarf Runtime
- 20. • Waiting fornew WildFly9 release • Improved Infinispan7 • Hibernate Search, Lucene upgrade • CapeDwarf Managed sub-project • Using GAE API directly in WildFly • Managed / Custom Runtime https://github.com/capedwarf/capedwarf-managed CapeDwarf WIP
- 21. 1. Download latestCapeDwarf release • http://www.capedwarf.org/downloads/ 2. Unzip & run • <CAPEDWARF_HOME>/bin/capedwarf.sh 3. Deploy your GAE app • Via WildFly management • Drop app into deployments/ dir Try it out!
- 22. • CapeDwarf • JBoss.orgforums • #capedwarf on Freenode IRC • capedwarf.org • ajustin@redhat.com Q&A