Lists Home |
Date Index |
- From: "David Orchard" <email@example.com>
- To: "KenNorth" <KenNorth@email.msn.com>, <firstname.lastname@example.org>
- Date: Tue, 8 Feb 2000 14:01:11 -0800
Ken, I absolutely agree with your comments. It's quite clear that smtp is
not quite business grade over the internet. You probably want to deploy MQ
series for really reliable, which is probably 15-25% of applications. As
you say, it's workable for many applications. But let's look at a bit more
industrial strength. Most MQ installs are within a firewall or a vpn. No
problems of viruses, untrusted hosts, etc. SMTP might be viable behind the
firewall for some fairly industrial apps. I'm not sure I'd trust $200 Mill
to it, but would you trust the cash to msmq on nt4 or CORBA on linux or HTTP
on whatever? I bet that smtp servers have had more effort put into
debugging/testing them than some of the current options. Again, there are
problems that you mention with load balancing.
Seems to me that SMTP could be extended in some of the industrial areas, or
it could be left to clever smtp app servers.
> -----Original Message-----
> From: email@example.com [mailto:firstname.lastname@example.org]On Behalf Of
> Sent: Monday, February 07, 2000 8:56 PM
> To: David Orchard; K.Kawaguchi; email@example.com
> Subject: Re: Asynchronous message queue by SMTP&POP3
> Subject: RE: Asynchronous message queue by SMTP&POP3
> Whether you need asynchronous messaging, queuing, and guaranteed delivery
> depends on in part on the nature of your application. Some people are
> looking at XML for mission-critical (bet-your-business) applications.
> > Some of the advantages and particular features:
> > o almost guaranteed delivery or notification of failure
> That's workable for many applications -- for example delivering news
> articles to a browser or a class schedule to a university
> student. If there
> is a delivery failure, I can always read it later.
> > Disadvantages:
> > o no server programming model - how does one program a java service at
> > firstname.lastname@example.org?
> > o not strong enough reliable delivery
> These are a problem if you want to use an XML infrastructure for
> mission-critical applications. For example, a major auto company processes
> many gigabytes of EDI transactions daily and there is a lot of
> momentum for
> moving to XML/EDI. You can't let $200 million in parts orders
> fall into the
> bit bucket. You'll need to do load balancing and custom document
> handling to
> get adequate performance with that type of application.