Ruby on Rails

There's some really interesting approaches in all of these emails.

I like this one the best. I haven't learned how to setup 2 databases
in rails... but is this complicated to do? I guess I could make a
database just like this person is doing, put all the thesaurus lookups
in it, and then keep it running just like any other database.

I want to avoid doing a ruby<->java bridge if I can. The last thing I
want is some bloated java process needing 512 megabytes of ram just to
do its think without throwing some kind of out of permgem space or out
of memory errors :/ At least if it's all in rails, I can just dedicate
all of extra ram to rails and my database.

Are the in-memory databases fairly quickly, such as sqlite? I've not
used it mysql. If it can take do at least 1000 individual select
statements very quickly (like less than a second), then that could
work.

On Apr 28, 11:26 am, Bill Walton <bwalton...@gmail.com> wrote:
> Hi Ken,
>
> On Thu, Apr 28, 2011 at 9:39 AM, egervari <ken.egerv...@gmail.com> wrote:
> > I have a program I'd like to write and I'd like to get off of Java and
> > start using something more productive. I have played around with
> > Rails, and I think I could the same app in a fraction of the time.
>
> Welcome!  I think you wouldn't have to look far to find any number of
> ex-Java developers on this list who could provide you with personal
> experience supporting your thinking. ;-)
>
> > There's one part of the app though that I am not if Rails/Ruby would
> > be a good fit... so I'd like to get some expert advice on this one
> > portion.
>
> > There's one part of the application that needs to check a thesaurus
> > about 100 or 200 times per request. There might be a lot of these
> > requests. There is also a grammar checker that is going to be used
> > (although I need to find one that works with Ruby).
>
> > I can imagine that these are some very expensive requests. In the java
> > world, I can simply put the thesaurus and grammar checker (with rules)
> > entirely in memory as Java beans in a spring container. When the app
> > starts up, we initialize these two services and they just stay in
> > memory, waiting for requests.
>
> I, too, will recommend a hybrid approach, though I suggest looking at
> an IMDB approach to the shared thesaurus.  Here's a link to one
> approach that looks ready-made for integration with a RoR app.http://www.themomorohoax.com/2009/03/15/activerecord-sqlite-in-memory...
>
> HTH,
> Bill

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.