Openstatus
www.openstatus.dev
fix: typo
+7
-6
+7
-6
apps/web/src/content/posts/global-latency-monitoring-benchmark-hono-hetzner.mdx
+7
-6
apps/web/src/content/posts/global-latency-monitoring-benchmark-hono-hetzner.mdx
···
11
11
tag: engineering
12
12
---
13
13
14
-
At OpenStatus, We offer **global monitoring** to give you an unbiased, external view of your service's performance. To truly test our monitoring capabilities and gather real-world latency data, we decided to benchmark a simple application deployed outside our internal network.
14
+
At OpenStatus, we offer **global monitoring** to give you an unbiased, external view of your service's performance. To truly test our monitoring capabilities and gather real-world latency data, we decided to benchmark a simple application deployed outside our internal network.
15
15
16
16
17
-
As software developer, I know that **latency** is critical for user experience. When building an application, understanding how your app performs from different locations around the world is essential.
17
+
As a software developer, I know that **latency** is critical for user experience. When building an application, understanding how your app performs from different locations around the world is essential.
18
18
19
19
## The Benchmark Setup
20
20
21
-
To prevent internal networking biases from skewing the results, I deployed a minimal test application a [**Hono server**](https://github.com/openstatusHQ/status-code/) on third-party cloud providers, independant from OpenStatus's infrastructure.
21
+
To prevent internal networking biases from skewing the results, I deployed a minimal test application a [**Hono server**](https://github.com/openstatusHQ/status-code/) on third-party cloud providers, independent from OpenStatus's infrastructure.
22
22
23
23
### Why Hetzner?
24
24
···
26
26
27
27
The test app is a single instance deployed in their **Finland datacenter**.
28
28
29
-
> ⚠️ **A Note on Deployment Experience:** The initial setup experience with Hetzner involved some friction, including KYC verification, which felt a bit dated. To manage the deployment, I opted to use **Coolify Cloud**, which helped bridge the gap, but the inner developer in me definitely missed the simplicity of a managed **PaaS** during the process.
29
+
> ⚠️ **A Note on Deployment Experience:** The initial setup experience with Hetzner involved some friction, including KYC verification, which felt a bit dated. To manage the deployment, I opted to use **Coolify Cloud**, which helped bridge the gap, but the inner developer in me definitely missed the simplicity of a managed **PaaS** during the process.
30
30
31
31
32
32
<Image
···
104
104
retry: 3
105
105
```
106
106
107
+
Note that non prefixed regions are Fly regions.
107
108
108
109
### Analyzing the Results
109
110
···
139
140
140
141
Through this global setup, I gained valuable insights into external network performance. I confirmed that the core challenge remains **geographic distance**, but the multi-provider approach helped us establish a **reliable baseline** for external connections. Developers can use this methodology to move past internal network bias and truly understand their app's latency profile from various points on the globe.
141
142
142
-
My 2cts ,if you want to pick a PaaS to deploy your next project, pick the one that fits your needs the best, because in the end, the network differences are minimal!
143
+
My 2cts, if you want to pick a PaaS to deploy your next project, pick the one that fits your needs the best, because in the end, the network differences are minimal!
143
144
144
-
If you want to try monitoring our app from multiple global locations, you can try our [global speed checker](https://www.openstatus.dev/play/checker) for free.
145
+
If you want to try monitoring our app from multiple global locations, you can try our [global speed checker](https://www.openstatus.dev/play/checker) for free.