Hi John,
We just released a product called Cloud2db which could fit very well in your
architecture if you are using JRuby. 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 Tue, Feb 23, 2010 at 1:56 AM, John777 <[email protected]> wrote:
> Hi Ikai Lan,
>
> Thanks for the excellent advice. I agree with you in the complexity
> that it will introduce by having this architecture. And thanks for
> giving some tips like Redis, Voldemor, etc.
>
> If any other people have more input, feel free to chime in
> John.
>
> On Feb 22, 6:56 pm, "Ikai L (Google)" <[email protected]> wrote:
> > I advise that you measure latency. Unless you run JRuby or Ruby 1.9,
> you're
> > going to run into an issue where you aren't able to handle many
> concurrent
> > requests. Phusion Passenger mitigates this slightly, but if you end up
> > making a lot of requests to an off box source, your front-end response
> time
> > will pay a price. There's definitely could be some benefit to doing this,
> as
> > if you wanted to do a lot of XMPP, it could make sense to use App Engine,
> > but if all you need is a horizontally scalable datastore, there's a lot
> of
> > work going into distributed key value stores like Redis, Voldemort (my
> > personal favorite), MongoDB, Cassandra, and so forth. By distributing
> your
> > architecture like this, you're likely making your code more complex than
> it
> > would otherwise need to be.
> >
> > Again, it's hard for us to give you a simple yes/no recommendation.
> You'll
> > have to look at your own needs and see if it makes sense. It shouldn't
> take
> > that long to whip up a simple REST interface on App Engine and something
> in
> > Rails that makes calls to this and generate load.
> >
> >
> >
> > On Mon, Feb 22, 2010 at 5:33 PM, John777 <[email protected]> wrote:
> > > additional info: In other words, the data subset in Google App Engine
> > > will be the one that subject to high traffic (probably from Android,
> > > blackberry or iphone). The front end in Ruby on Rails will not be that
> > > high traffic. So, by having this type of architecture, I have the best
> > > of both world. The flexibility of front end on hosting site and the
> > > scalability of Google App Engine on the backed site.
> >
> > > On Feb 22, 5:22 pm, John777 <[email protected]> wrote:
> > > > Thanks guys for the answer.
> >
> > > > So this will be the scenario
> > > > Ruby on Rails (on hosting site) <-> internet (push/pull) (REST) <->
> > > > python in Google App Engine.
> >
> > > > I think you nail the question why I want to use Ruby on Rails on the
> > > > front end because I feel "app engine java" is not that reliable yet.
> > > > At the same time Ruby On Rails on the hosting give me a lot of
> > > > flexibility. By putting certain type of data in Google App Engine, it
> > > > will be standard for all other devices that need to access that set
> of
> > > > data. Like from Android, blackberry, iphone, etc.
> >
> > > > One of the problem that might come out is data sync from hosting site
> > > > and Google App Engine site.
> >
> > > > What do you think? or what other possible issues that might come out
> > > > with this scenario?
> >
> > > > Thanks,
> > > > John
> >
> > > > On Feb 22, 2:34 pm, Locke <[email protected]> wrote:
> >
> > > > > If what you're saying is that you want to use appengine to host web
> > > > > services (REST or some dialect of XML) then my answer is: sure, go
> > > > > ahead, so long as you use Python. In my experience, appengine's
> java
> > > > > support is unreliable: simple java apps are occasionally killed for
> > > > > "excessive latency," and sometimes they just load really slowly.
> >
> > > > > And if you want to implement your web services in JRuby, you have
> the
> > > > > same problems with java, but to a greater degree (as jruby is
> > > > > essentially a really big java library).
> >
> > > > > So: either use Python or wait to see if google adds support to keep
> > > > > Java apps loaded.
> >
> > > > > On Feb 22, 12:47 pm, John777 <[email protected]> wrote:
> >
> > > > > > Hi,
> >
> > > > > > I am planning to use Ruby on Rails on other hosting site and
> > > push/pull
> > > > > > some of data to/from Google App Engine. Do you guys think it is a
> > > good
> > > > > > idea?
> >
> > > > > > Thanks,
> > > > > > John
> >
> > > --
> > > You received this message because you are subscribed to the Google
> Groups
> > > "Google App Engine" group.
> > > To post to this group, send email to [email protected]
> .
> > > To unsubscribe from this group, send email to
> > > [email protected]<google-appengine%[email protected]>
> <google-appengine%[email protected]<google-appengine%[email protected]>
> >
> > > .
> > > For more options, visit this group at
> > >http://groups.google.com/group/google-appengine?hl=en.
> >
> > --
> > Ikai Lan
> > Developer Programs Engineer, Google App Enginehttp://
> googleappengine.blogspot.com|http://twitter.com/app_engine
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<google-appengine%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
