[AccessD] Another software disaster...

Jim Lawrence accessd at shaw.ca
Mon May 21 19:36:11 CDT 2012


Hi Darryl:

You have about summed it. Some of these systems took 20 years to get all the
bugs out and any new system would have to go through the same vetting
process.

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins
Sent: Monday, May 21, 2012 4:00 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Another software disaster...

Interesting stuff.  I think a huge part of it (I know it is for the Banks in
Oz) is fear of stuffing us the existing system.  It maybe slow, it maybe
old, it maybe written in FORTRAN, but it has been debug to hell and bug and
it does work and has for decades now.  No-one want to take the
responsibility of stuffing up the system. 

I know in Australia the big banks are slowly updating their main legacy
platforms, and it hasn't been without some major outages and issues.  These
always cause a big public and media stir and I guess also raises issues of
trust and integrity.

A risky path for any business...

Cheers
Darryl

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Tuesday, 22 May 2012 2:03 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Another software disaster...

My personal belief is that the systems that runs the stock-exchange are old,
main frame old. 

The software is probably some ancient procedure driven language, not a queue
driven one. Stock-brokers like accountants are very slow at updating their
systems. I do work for local banks from time to time and some of the main
software packages, that run everything were creates over 50 years ago. These
packages may be running on Unix servers but they are not modern distributive
packages so when they meet the system's (hardware) maximum capability they
just loops. 

The requirements of an operation like the Stock-Exchange are far beyond the
capabilities of old database structures like MS SQL or even Oracle. The
Facebook or Google software team should be ones writing new code on their
database systems...their databases don't even flinch when managing a billion
consecutive hits.   

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: Monday, May 21, 2012 4:28 AM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Another software disaster...

This time it was a design issue..that testing did not uncover.

I smell something here..I think there's more to it.

http://www.bloomberg.com/news/2012-05-20/nasdaq-ceo-says-poor-design-in-ipo-
software-delayed-facebook.html

Outsourcing involved ? No one is saying..

 

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list