Log in

No account? Create an account
entries friends calendar profile My Website Previous Previous Next Next
Do banks really use strict old-skool transactional RDBMSs? - Mark Atwood — LiveJournal
Do banks really use strict old-skool transactional RDBMSs?
8 comments or Leave a comment
blarglefiend From: blarglefiend Date: April 15th, 2009 04:59 am (UTC) (Link)
A lot of it is familiarity. A transactional RDBMS provides some of the tools to support "average programmers", and also for "better than average programmers" having a bad day. It's not that you can't do this stuff without one, just that that's the support tool a lot of people in this space are used to.

I work for a reasonably large financial services firm. Some of our programmers are really good, and some are... less so. We've got guys who "need" a PHP wrapper to send email (running on a UNIX host, the rest of the app is not written in PHP), we've got guys who can't see that running a big query where all fields referenced aren't indexed is going to be slow, and so on.

If you start out with an RDBMS you might as well stick with one. If you started long before those were around, well, of course migrating to one is probably going to cost more than it's worth.

Porting our code from Sybase to Oracle would be painful but not impossible. Porting to something radically different would be a much bigger job, and probably not worth the cost.
8 comments or Leave a comment