<snip>
>
> MySQL is small, fast and stable. But it is not a full blown database
> system such as IBM DB2 etc
>
> It can not do 'rollbacks' but since neither can the the web, who
> cares???
I am shocked.... (Pause to collect myself). You need transactions
(rollbacks) for various reasons, as Rick has explained. More, if you are
abstracting your business logic and you do perform any decent multi table
access across your domain objects.
A simple example : if you do an acct. transfer in a bank, it internally does
a withdrawal and a deposit and say the deposit failed for some reason (disk
full), then you really want you money back in your transferred from account,
would'nt you.
> My original question is how can you use the web for 'mission critical'
> transactions?
>
> IBM (Web Sphere)is trying multiple abstraction layers and Java to
> confirm transactions but trying to understand it makes SNA look easy.
>
WebSphere is a J2EE (nearly) compliant Appplication Server. Thus, it follows
the J2EE APM of using Servelets/Beans/JSP's for persentation, EJB's for
business logic and data abstracion layers.
Now, you may not need all of these for a simple web app, but if you are
building an Enterprise wide app, that needs to access different mainframes,
databases, do 2phase commit across databases, you need a product like
WebSphere to do app server clustering/load balancing etc. for 24x7 access.
You pick and chooses what you need. For a low volume, non 24x7 site, you can
use the SE with just servlets. For more robust apps, you can use the AE or
EE with EJB support etc..
-- Aravind
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to [EMAIL PROTECTED] with
unsubscribe in the text
