|
Scalability
 |
Scalability is designed into Board from the core and from every layer. From application performance to database design to RAM and processing power to network communications considerations, Board optimizes and delivers powerful scalability.
- Application scalability: the usual trade-off between performance
that requires aggregated data and the
need for detail is resolved by the Parent-Child
database architecture. Users view the two or
more databases within the application
transparently and can seamlessly navigate,
run analysis and drill-down from the parent DB containing
summarized data, to the Child DB holding
the desired detail level of data (transaction
level).
- Database scalability: multi-dimensional databases are known
to suffer limitations in the size and
the detail of the data that they can
manage. Most multi-dimensional databases have intrinsic
limitations which cannot be compensated
simply by adding more hardware. Board’s MDB breaks this limitation,
commonly handling InfoCubes having several
million members (distinct item codes) per dimension.
- Low RAM requirements: unlike many, Board’s MDB is not
RAM based, meaning that data volumes
can freely grow beyond what RAM can manage.
- Processing power: the BoardMaster program incorporates a sophisticated
and robust dynamic load-balancing capability
that supports server clusters when more processing power is required.
- Low network traffic: thanks to the highly compressed ROAR protocol,
even a high number of users have limited
impact on your network.
|
|
|
|
Performance
Scalability