Reposting since this seemed to have gotten lost in the stream :)
I'm trying to build a stand alone application where I have multiple
threads or actors that subscribe to a queueing system and persist stuff on a
database. Does it make sense to use mapper here? I ask because of this stack
overflow
post.http://stackoverflow.com/questions/1140448/what-orms-work-well-with-scalaIn
terms of our requirements, what we want from an orm is fairly basic.
Since we are not building a web application, we would want it decoupled from
any other parts of such a stack. (I heard mapper depends on the http
module?). We need most of the basic orm operations with ACID compliance,
preferably one that requires us to write as little code as possible and
includes transactionality as something we can depend upon. The database
we're currently looking at is Postgresql, so ideally the ORM should be
oblivious of whether or not the database is distributed.> > On Tue, Jan 5, 2010 at 6:39 PM, Timothy Perrett > <[email protected]>wrote: > >> In what way do you mean "is mapper worth it"? >> >> What kind of system is it? do you need ACID or BASE? What kind of load >> will the system be under? Do you need it to be distributed? You are >> not restricted to Mapper, you could use JPA or whatever persistence >> you want with lift. >> >> If you just want to make a pretty simple service tier, then sure, Lift >> will be fine. Akka works well when you need fault tolerance or >> distributed nodes etc etc >> >> Cheers, Tim >> >> On Jan 5, 3:34 am, vishnu <[email protected]> wrote: >> > well I'm not sure how to describe it differently. As you said it's only >> > service tier. The truth is I dont know anything about Lift yet and Im >> just >> > now running through some basic Scala books. >> > >> > I need a library with which to talk to rabbitmq as a subscriber that >> might >> > work at a higher level than the default java api that comes with >> rabbitmq >> > and ideally something that provides the same service for me talk to a >> > database via scala. I haven't seen Akka before, so I'll take a look at >> that >> > :). Would you say mapper is worth it? >> > >> > On Tue, Jan 5, 2010 at 2:23 AM, Timothy Perrett < >> [email protected]>wrote: >> > >> > >> > >> > > It depends on your use case... you don't really describe exactly what >> you >> > > want to do. Perhaps start by providing more detail? If you want >> service teir >> > > *only* though, its quite probable that akka would be a better fix. >> > >> > > Cheers, Tim >> > >> > > On 4 Jan 2010, at 20:30, Channing Walton wrote: >> > >> > > > Maybe Akka would be better for you?http://akkasource.org/ >> > > > "Akka has an AMQP module which abstracts AMQP Producer and Consumer >> as >> > > > Actors." >> > >> > > > Channing >> > >> > > > vishnu-11 wrote: >> > >> > > >> Hi >> > > >> I'm trying to use lift to right a back end for a system that >> > > >> communicates via AMQP. The idea is to have a bunch of (threads?, >> > > >> processes? actors?) that subscribe to some queues on a queueing >> system >> > > >> and react to various messages by contacting various third party >> > > >> systems and persisting messages to a database. >> > >> > > >> I was wondering firstly if it makes sense to use lift, or if it >> makes >> > > >> more sense to pull various parts out of lift and use them? >> > >> > > >> Additionally, looking at the lift amqp code, it seems to be a >> little >> > > >> out of date, especially with regard to amqp. Does anyone know if >> there >> > > >> has been any active work on this segment? >> > >> > > >> -- >> > >> > > >> You received this message because you are subscribed to the Google >> > > Groups >> > > >> "Lift" group. >> > > >> To post to this group, send email to [email protected]. >> > > >> To unsubscribe from this group, send email to >> > > >> [email protected]<liftweb%[email protected]> >> <liftweb%[email protected]<liftweb%[email protected]>> >> > > . >> > > >> For more options, visit this group at >> > > >>http://groups.google.com/group/liftweb?hl=en. >> > >> > > > -- >> > > > View this message in context: >> > >http://old.nabble.com/Lift-based-backend-server-subscribing-via-amqp-. >> .. >> > > > Sent from the liftweb mailing list archive at Nabble.com. >> > >> > > > -- >> > >> > > > You received this message because you are subscribed to the Google >> Groups >> > > "Lift" group. >> > > > To post to this group, send email to [email protected]. >> > > > To unsubscribe from this group, send email to >> > > [email protected]<liftweb%[email protected]> >> <liftweb%[email protected]<liftweb%[email protected]>> >> > > . >> > > > For more options, visit this group at >> > >http://groups.google.com/group/liftweb?hl=en. >> > >> > > -- >> > >> > > You received this message because you are subscribed to the Google >> Groups >> > > "Lift" group. >> > > To post to this group, send email to [email protected]. >> > > To unsubscribe from this group, send email to >> > > [email protected]<liftweb%[email protected]> >> <liftweb%[email protected]<liftweb%[email protected]>> >> > > . >> > > For more options, visit this group at >> > >http://groups.google.com/group/liftweb?hl=en. >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "Lift" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<liftweb%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/liftweb?hl=en. >> >> >> >--
You received this message because you are subscribed to the Google Groups "Lift" 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/liftweb?hl=en.
