Laravel Cloud · multi-language demo

Multi Language Showcase

This dashboard fans out to eleven applications written in six languages — PHP (twice), Ruby, Go, Python, Java and JavaScript (five times, across two runtimes) — all running together in one Laravel Cloud environment, all sharing one managed Postgres database, and all implementing the exact same HTTP contract.

Live status

Click a chip to fire one real request between two live services — no arming, no modes. The result lands right on the card. “Run the mesh” fires the same real requests, one at a time, between the peer services so you can watch the path move without clicking anything.

service-php

healthy
language
PHP
runtime
8.5.10
framework
none
region
eu-west-2
uptime
71690s
memory (rss)
26 MB
memory (own)
2 MB
boot
no process boot — per-request runtime
cpus
1
cpus (host)
4
latency (15m)
not enough data yet (3 samples in 15m)
fan-out
2083ms
message
Hello from PHP on Laravel Cloud

△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.

call →

service-ruby

unreachable

unreachable — cURL error 28: Operation timed out after 2000 milliseconds with 0 bytes received (see https://curl.se/libcurl/c/libcurl-errors.html) for https://polyglot-ruby-main-rhf0mh.laravel.cloud/info

call →

service-go

healthy
language
Go
runtime
go1.26.8
framework
net/http
region
eu-west-2
uptime
71848s
memory (rss)
8.9 MB
memory (own)
1 MB
boot
10ms
cpus
1
cpus (host)
4
latency (15m)
not enough data yet (3 samples in 15m)
fan-out
2083ms
message
Hello from Go on Laravel Cloud

△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.

call →

service-python

healthy
language
Python
runtime
3.12.14
framework
FastAPI
region
eu-west-2
uptime
119889s
memory (rss)
49 MB
memory (own)
58.8 MB
boot
1.13s
cpus
1
cpus (host)
4
latency (15m)
not enough data yet (3 samples in 15m)
fan-out
2083ms
message
Hello from Python on Laravel Cloud

△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.

call →

service-java

healthy
language
Java
runtime
21.0.12
framework
Spring Boot
region
eu-west-2
uptime
71841s
memory (rss)
187.2 MB
memory (own)
27.3 MB
boot
8.98s
cpus
1
cpus (host)
4
latency (15m)
not enough data yet (3 samples in 15m)
fan-out
2083ms
message
Hello from Java on Laravel Cloud

△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.

call →

service-javascript

degraded
language
JavaScript
runtime
v22.23.2
framework
none
region
eu-west-2
uptime
71848s
memory (rss)
53.4 MB
memory (own)
13.5 MB
boot
140ms
cpus
1
cpus (host)
4
latency (15m)
not enough data yet (0 samples in 15m)
fan-out
2083ms
message
Hello from JavaScript on Laravel Cloud

△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.

⚠ can serve requests but cannot reach the database

call →

service-bun

degraded
language
JavaScript
runtime
1.4.2
framework
none
region
eu-west-2
uptime
71842s
memory (rss)
28.3 MB
memory (own)
8.1 MB
boot
200ms
cpus
1
cpus (host)
4
latency (15m)
not enough data yet (0 samples in 15m)
fan-out
2083ms
message
Hello from Bun on Laravel Cloud

△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.

⚠ can serve requests but cannot reach the database

call →

service-elysia

degraded
language
JavaScript
runtime
1.4.2
framework
Elysia
region
eu-west-2
uptime
71842s
memory (rss)
35.4 MB
memory (own)
6.8 MB
boot
290ms
cpus
1
cpus (host)
4
latency (15m)
not enough data yet (0 samples in 15m)
fan-out
2083ms
message
Hello from Elysia on Laravel Cloud

△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.

⚠ can serve requests but cannot reach the database

call →

service-hono

degraded
language
JavaScript
runtime
v22.23.2
framework
Hono
region
eu-west-2
uptime
71847s
memory (rss)
35.2 MB
memory (own)
12.3 MB
boot
200ms
cpus
1
cpus (host)
4
latency (15m)
not enough data yet (0 samples in 15m)
fan-out
2083ms
message
Hello from Hono on Laravel Cloud

△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.

⚠ can serve requests but cannot reach the database

call →

service-nuxt

degraded
language
JavaScript
runtime
v24.21.0
framework
Nuxt
region
eu-west-2
uptime
71809s
memory (rss)
57.6 MB
memory (own)
19.4 MB
boot
38.51s
cpus
1
cpus (host)
4
latency (15m)
not enough data yet (0 samples in 15m)
fan-out
2083ms
message
Hello from Nuxt on Laravel Cloud

△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.

⚠ can serve requests but cannot reach the database

call →

service-rust

healthy
language
Rust
runtime
1.98.1
framework
axum
region
eu-west-2
uptime
71847s
memory (rss)
4.5 MB
memory (own)
0.4 MB
boot
20ms
cpus
1
cpus (host)
4
latency (15m)
not enough data yet (3 samples in 15m)
fan-out
2083ms
message
Hello from Rust on Laravel Cloud

△ marked figures are measured identically in every service and are directly comparable; unmarked ones (memory (own)) are each runtime's own accounting.

call →

Build & deploy time

Laravel Cloud's own end-to-end build-and-deploy duration for each app — compile, image build, push and rollout, not just a compile step. Polled from the Cloud API every few minutes by a scheduled job and cached here; this page never calls that API itself.

Build times unavailable — no Cloud API token is configured yet.

Live activity

Live — updates every few seconds