Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

SolarWinds APP server location is on-prem and DB is on cloud

sw44

SolarWinds APP server location is on-prem and DB is on cloud. 50 ms between both servers.

Should it be good?

Does anyone have some experience with this architecture?

Thanks

Find more posts tagged with

Accepted answers

All comments

stevenstadel

Yes, you should be good. Official recommendation

The latency (RTT) between each SolarWinds Platform engine and the database server should be below 200 ms. Degradation may begin around 100 ms, depending on your utilization and the size of your deployment

cnorborg

Maybe good by the official recommendation, but I wouldn't recommend it! Would probably be better off putting the App server in the cloud near the server, and getting an additional poller to put remotely if you need to.

When loading a webpage, the app server makes quite a few queries to the DB server, adding 50ms of latency to those queries doesn't sound good to me!

m_roberts

50ms is pretty low and we have customers deployed in this manner that do not experience issues. However, I agree with @cnorborg, the Main polling engine (MPE) and web servers are better placed close to the DB server. If you are running under HCO or NAM licensing, there is no restriction on the number of additional polling engines (APE) and therefore this gives great architecture flexibility, where you may have your MPE sat in cloud with the SQL DB and then use APE(s) on prem to collect local data.