9 Replies Latest reply on Feb 26, 2014 3:57 AM by Mike Jones

    Small bladelogic deployment

    Jim Campbell

      I know the recommended architecture for a Bladelogic deployment is to have a low-latency connection between the application server and the database server.  However, for a small (~100 servers) deployment in a segregated environment in a remote site we have two options:


      1) Database server and Bladelogic application server on the same server at the remote site

      2) Bladelogic application server connecting to enterprise database server over a connection with some latency (probably about 20ms)


      At present we plan only patching and maybe some ad hoc package deployments for these servers (i.e. no provisioning).  Would we be better off putting the database on the same server to preserve the low latency link between the application and database or preserving the performance of the application server by hosting the database on a separate datbase server?