On 11/5/05, Barney Boisvert <[EMAIL PROTECTED]> wrote:
> Depends on what you mean by ORM.

Hey! "It depends" is *my* catchphrase!

> Things like Arf! or Reactor start to
> encroach on that space.  Certainly not a conventional ORM solution,
> but they provide many of the benefits.  No idea about scalability, but
> I suspect Reactor will be quite performant, since it does very little
> at runtime.  I'm not sure about Arf!'s execution profile as I haven't
> dug into the implementation as far.

I haven't looked at Reactor much.

Arf! is definitely not something to build large-scale high-traffic
apps from - in the same way that Rails is not either. Those are both
quick ways to build standard CRUD apps against a database. I would not
expect those to scale. And then there's the whole issue of driving an
app from the database (as opposed to designing an efficient database
schema to persist your well-designed object model).

Arf! (and Rails) definitely have a useful niche. I'm building a
Model-Glue / ColdSpring / Arf! content management app right now for a
website I built a while back (I've been using a desktop DB management
app for getting data into the site so far - don't ask!). It's an admin
app so it's very low traffic. To be honest, even the public-facing
part of the site is fairly low traffic so it wouldn't hurt to use Arf!
for that too I suspect, but I already built that using Fusebox and
some CFCs (DAO / gateway stuff).

Once I've gotten my head around Arf! I will probably go back and look
at Reactor again in more detail.
--
Sean A Corfield -- http://corfield.org/
Got frameworks?

"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood


----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to 
[email protected] with the words 'unsubscribe cfcdev' as the subject of the 
email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting 
(www.cfxhosting.com).

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]


Reply via email to