Skip to content

6 months on a 'cloud' shared plan vs traditional

Web Hosting by LichunLars 6 replies 436 views
4 #1

Went with GreenCloudVPS's "elastic cloud shared" plan in January. Marketing promised "seamless scaling" and "distributed redundancy." Six months later, rewriting this post because I finally understand what I bought.

The problem: every request hits a different node. Session files vanish between clicks. Upload a file, 404 on refresh. Route via their Anycast adds 8-12ms vs my old InterServer VPS, but that's not the real issue.

$ for i in {1..5}; do curl -sI https://greencloudvps.com | grep -i "X-Served-By"; done
X-Served-By: node-pdx-47
X-Served-By: node-atl-12
X-Served-By: node-pdx-03
X-Served-By: node-ord-89
X-Served-By: node-pdx-47

"Elastic" meant they spin containers per-request, not that my plan scales. My bad for not reading. Traditional VPS: one box, predictable sessions, 0ms node hopping.

Updated my review. They updated their sales page too. Coincidence?

1ms or I don't want it
#2

Different, "cloud" is marketing cloud, not architecture cloud. Your session need redis going to fix. One box going to break when scale.

one small ping for man...
#3

Thank you very much sir armstrongvds

Redis is extra cost at GreenCloudVPS sir, not included in shared plan. My old InterServer VPS never had this session problem

Very confusing for small project like mine

traffic worse than my packet loss
11 #4

Cara, I going to tell you what happen here véi

This "cloud" word mean nothing now kkkkk

You need sticky sessions or external cache solve this kkkkk

I going to stay on my Time4VPS VPS, one box only, no surprise kkkkk

chill infrastructure for chill people 🦫
2 #5

---
LichunLars:
- experience: valid
- diagnosis: incomplete
---
Architecture:
- "cloud" as marketing: yes
- "cloud" as distributed systems: also yes
- GreenCloudVPS implementation: stateless containers
- NOTE: not actually elastic scaling
---
Solutions:
- sticky sessions: works, breaks "elastic" claim
- external session store: redis, postgres
- object storage for uploads: S3-compatible
- WARNING: all add cost, complexity
---
My setup:
- RackNerd traditional VPS
- container orchestration: docker-compose
- scaling: manual, known limits
- latency: consistent, measurable
---

indentation is not optional
#6

8-12ms? I'd want to see that benchmarked against the same DC

#7

Which kernel was the InterServer running?

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft