Hi Jacob,
We just released a product called Cloud2db which could fit very well in your
architecture. Here are some details.
Cloud2db Server provides a standards-based abstraction layer over Google
Datastore (Bigtable). This product provides you with performance and
scalability of GAE along with structure, standards and interoperability of
RDBMS, SQL and JDBC.
With Cloud2db, you will be able to manage your data on Google Datastore by
using established concepts of RDBMS, SQL and JDBC, and thereby preserving
your existing investments in tools, technologies, frameworks and skills.
Here are Cloud2db features:
- Manage data on Google Datastore using familiar concepts of RDBMD, SQL
- Referential integrity (Primary Keys, Foreign Keys)
- Role Based Security
- Joins (Inner Join, Left Outer Join, Theta Join, Cross Join)
- Subqueries (Exists, Not Exists, In)
- DDL & DML
- Transactions
- ANSI SQL stored functions
- Views
- BLOB and CLOB support
- Use any JDBC compliant tools and frameworks in the market to interact
with the Google Datastore. For example.
- Squirrel SQL (database management)
- Power Architect (data modeling)
- Jasper Reports (reporting)
- Hibernate (Object To Relational mapping)
- All JDBC compliant tools
- Port exiting RDBMS instances to Google Datastore
Please visit our website http://www.cloud2db.com and try out the free trial
version of our product by registering at
http://cloud2db.appspot.com/website/registration.html. Please visit google
group Cloud2db <http://groups.google.com/group/cloud2db> to share your
feedback and thoughts.
Sincerely,
Sandeep Sathaye
Founder and Chief Architect
Cloud2db
On Fri, Mar 5, 2010 at 7:54 AM, vennervald <jacob.vennerv...@gmail.com>wrote:
> Hi Guys
>
> We have a small application running on JBoss, Seam, Hibernate and
> PostgreSQL that we are thinking about moving to GAE/J.
> To test the datastore we uploaded our data 1-1 so all our tables from
> Postgres were represented as entity types in the datastore with the
> entities relating to eachother through their keys.
> As a proof of concept of the performance of the datastore, we did an
> implemented one of our heaviest reports by joining 6 entities
> together. And the performance proved to be really bad. Infact we
> received the deadline exception before we got to join all the
> entities. From the platform we are running on now, this could be done
> in less than a second.
> This doesn't tell me that Google datastore is worthless. It tells me,
> that I'm doing something wrong, and that I need to think differently
> about the data structures to make it perform on GAE.
> I've been looking around and I can't seem to find really good sources
> on datastore/JDO best practises.
> Does anybody have any good resources on this toppic?
> I would really apriciate your help.
>
> /Jacob :)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine for Java" group.
> To post to this group, send email to
> google-appengine-j...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine-java+unsubscr...@googlegroups.com<google-appengine-java%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
