Tell me more ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I am a student, and have a question for an assignment:

What problems and challenges do database administrators face when designing systems to trade international stocks in real time and 24 hours a day, 6 days a week? Are cloud based database systems as a service a viable option?

share|improve this question
For one thing, you're looking at a very intermittent maintenance window. You may think 24 hrs / week is a good ratio, but not when that a maintenance window is a max of 6 days away. As far as the "cloud", that word has been thrown around countless times with very different definitions, so you'll have to specify exactly what you mean by "cloud". – Thomas Stringer May 17 '12 at 1:10
1  
The number 1 concern of course is uptime. You're looking at a very demanding SLA. – MarlonRibunal May 17 '12 at 1:24
1  
Your system would need to be absolutely stable and rock solid. As such, you want to avoid rapidly evolving systems that keep changing all the time, with likely frequent breaking changes. Google up "breaking changes" followed by the name of whatever cloud you mean, and see for yourself. – AlexKuznetsov May 17 '12 at 3:07

1 Answer

Because it's a system, you will have a LOT of interacting subsystems, including power, environmental controls, communications, hardware, and then on top of that the data management and everything else.

There are facets which cut across all these layers, like security, redundancy, business continuity, etc.

Just from the database side, you would need to consider the transactional load, the architecture for balancing the load, the storage requirements, the response time requirements.

Everything depends upon the requirements - of which there will be many from regulatory bodies, clients, users, business partners.

As to whether cloud-based databases, I don't think any of those can be viable if your organization has to be responsible for the system.

Any time you outsource anything, you limit your ability to be responsive to requirements. Some things you delegate are easier to mitigate than others. For instance, you decide to use a software library as a component in your system - you can always modify the library if you have the source, or rewrite it yourself or swap it out. Or picking a RDBMS like Oracle or SQL Server where you can get a vendor to do a proof of concept and have a high level of support because the sale is large.

That's not to say by relaxing your requirements, you couldn't use Google Apps BigTable or Amazon or Azure or whatever, but the simple fact is that even with a contract, you have a limited amount of control over another organization's system and you are relying on them.

All systems are built by balancing tradeoffs.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.