How does Base One avoid a bottleneck at the central database?
Every DBMS has performance pitfalls, which lead even experienced programmers into designing applications that scale poorly or tend to produce deadlocks. Base One’s Database Library, at the heart of its grid processing middleware, has been carefully optimized for each supported DBMS, to achieve reliable transaction processing with a minimum amount of database locking. This makes it easy to build efficient, scalable applications without falling into the usual subtle traps. For example, a common mistake is the over-use of cumbersome, distributed transaction processing (XA) protocols in message-based architectures. The greater economy of Base One’s approach is possible, because the Virtual Supercomputer relies upon a centralized database, even though processing power and temporary storage may be widely distributed. Of course any database ultimately could be swamped by excessive load, but the capacity of a database server generally can be increased far more easily than upgrading the rest of
Related Questions
- I do not want to give the database password to people who are simply viewing reports with cView. How do I avoid giving it out, without losing functionality?
- Do I need to enter the Operating System Base License PAK into the license database for each partition on a system?
- How to avoid that more than one database record has the same ecord name?
