Quercus/GAE at Google I/O x2, with a cool new demo!
The nice folks organizing the Google I/O conference have given us an extra day to demo Quercus on the App Engine, so Nam and I’ll be there both Wednesday (12-6pm) and Thursday (12-4:45). It’s perfect timing too, because Nam has just finished an incredible demo that goes way beyond my meager efforts. He’ll be writing up a blog post about it soon, so I’ll have to just leave you in suspense until then…
Tags: google app engine, quercus

May 26th, 2009 at 10:19 pm
My bet is that Nam has written a GAE driver for PDO … so that many PHP applications can be installed on GAE.
And when there is a SQL “CREATE TABLE” statement he calls the JDO 2.3 metadata API, so there is no need anymore to write a Java class with annotations for every table you want to use in PHP scripts.
just dreaming, in the mean time I’m working on below project, better parsing, better error handling, better log messages.
http://blog.herbert.groot.jebbink.nl/2009/05/sql-to-jdo-for-php.html
May 31st, 2009 at 3:11 am
Good idea but I think the problem with a GAE to JDO/JPA adapter is that GAE uses Data Nucleus for it’s JDO implementation and Data Nucleus requires a post compile step to ‘enhance’ classes before it’s usable by GAE. I am not sure how to do this at runtime.
What we have planned is similar in purpose. We have our own implementation of a SQL database that we can adapt to stores itself into Google Datastore. I think that would be much easier for us to implement.
May 28th, 2010 at 7:20 pm
We’re really excited about this and looking at it as the leading choice for GAE development.
We did some GAE response-time tests today with Resin 4.0.7 which I downloaded from Caucho (I believe that the version I downloaded includes the open source/free version of Quercus) and we can see the servlet loading time is the biggest delay, but Google has a paid feature on the roadmap for GAE to reserve the JVM, which should keep the servlet loaded. Otherwise, it’s in the double digit milisecond range per request (have yet to do datastore tests)
Questions:
1) Will the open source/free version of Resin/Quercus for GAE include the SQL support?
2) When do you believe you’ll finalize the billing model for the paid version of Resin/Quercus for GAE?
A suggestion we have regarding the paid version is to have a free quota with it, so it’ll be compatible with the GAE freemium model, and users can experiment with building solutions and testing them out on GAE without being charged for development time/low usage.
Thanks in advance for your answers.
Julio Rodriguez
Sr. Web developer