Biomedical Engineering Reference
In-Depth Information
need to be scalable and fast. But one must be sure to add the relevant
amount of power in the relevant places. As an example, what happens if
the corporate database is unavailable for a couple of days? Scientists can
continue their lab experiments, can read or write papers and prepare
their next presentation. The research organisation does not come to a
complete stop. Is 99.99% availability really needed and does it make
sense to pay the premium to get the last very expensive parts covered?
The experience of our group suggests otherwise, we assert that many
of the relevant open source tools are suffi ciently stable and scalable to
meet the needs of pharmaceutical research.
After these considerations - and some initial reading about the different
tools, to understand how they really worked, and try to get a feel for the
level of activities in the different communities - it was decided to go with
the stack outlined in Figure 1.1 and described in detail below.
1.5.1 Database
When deciding on the LSP stack, a database change was ruled out. The
Oracle database is one of the exceptions from the fully open source stack
mentioned in the introduction. It would be natural to build LSP on top of
an open source database but at the time a deliberate decision was made
to continue our use of Oracle. As the Lundbeck corporate IT standard
Technology stack of the current version of LSP running
internally at Lundbeck
Figure 1.1
Search WWH ::
Custom Search