Oracle Woe's - Pam Issue?

[Mike Garfias]

You're missing the point.  You can scale beyond a single box without  
getting into some complex clustering setup AND without getting into  
expensive hardware.  It just requires work in the dev cycle, rather  
than SA work after the app is built.

I'm not telling him to use MySQL, Postgres, or even oracle.  I'm  
suggesting he change the way he looks at the databases which in the  
long run could save lots of pain.

On Dec 12, 2007, at 9:39 PM, Dan Lund wrote:

> On Dec 12, 2007 7:43 PM, Mike Garfias <mike at garfias.org> wrote:
>> Bryan -
>>
>> In my experience you'll be far better off NOT relying on one killer
>> database box (or even a cluster) to handle all your data.  HW only
>> scales so far before it gets too expensive.
>
> In my experience, choosing a database based upon your needs is the
> best way to go.
> Hardware never scales beyond being too expensive, because once you
> scale beyond a single box worth of queries, you either choose to limit
> the queries or start to scale to a cluster.
> It's pretty much as simple as that.
>
> -- 
> Thanks,
> Dan Lund
>
> "This day we rescue a world from mysticism and tyranny, and usher in a
> future brighter than anything we can imagine."
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
> !DSPAM:14,4760b79f50041786066171!
>
>