Aether is the unified application runtime for Java. One system replaces your entire infrastructure stack. Write business logic as typed interfaces. The runtime handles everything between your code and production.
@Slice
public interface OrderService {
Promise<OrderResult> placeOrder(PlaceOrderRequest request);
static OrderService orderService(InventoryService inventory,
PricingEngine pricing) {
return request -> inventory.check(request.items())
.flatMap(pricing::calculate)
.map(OrderResult::placed);
}
}
Write an interface annotated with @Slice. Aether handles distribution, scaling, resilience, observability, and zero-downtime deployments.
No HTTP clients. No service discovery. No retry logic. No circuit breakers. No serialization code. A method call is the only visible contract.
Docker cluster, real PostgreSQL, mixed read/write workload, laptop (i7-11800H, 32GB).
Every Java service you deploy carries a hidden cost.
Container orchestration, service mesh, config management, secret rotation, certificate management, schema migrations, connection pooling, load balancing. A platform team becomes mandatory just to keep Java services running.
Every microservice bundles web servers, serialization, DI containers, service discovery, metrics, and retry logic. Infrastructure and business logic compile together, deploy together, break together. A security patch means rebuilding every service.
A typical Java microservice exposes 580-820 configuration surfaces. Multiply by the number of services, multiply by the number of environments. Managing this becomes a full-time job.
One runtime. One configuration. One deployment command.
| You currently manage... | Aether handles it |
|---|---|
| Container orchestration | Declarative cluster management |
| Java frameworks | Slice model + resource provisioning |
| Application-scale streaming | Built-in ordered, replayable streams |
| Distributed caching | Consensus-backed KV-Store + DHT |
| Service mesh | Built-in mTLS, routing, load balancing |
| Schema migration tools | Blueprint-bundled migrations |
| Connection poolers | Async driver with pipelining |
| Config & discovery services | Consensus KV-Store |
| Certificate management | HKDF-derived certs, auto-rotation |
Teams are pushing back on operational complexity. The question shifted from "how do we run more tools?" to "how do we run fewer?"
Major acquisitions and team cuts in the streaming space are forcing enterprises to re-evaluate their event infrastructure.
Organizations are asking: "do we really need all these managed services?" Self-managed deployment that's just as easy changes the math.
Three environments, zero code changes.
Embeddable runtime. Multiple logical nodes in one JVM. Standard debugger. The zero-risk entry point for legacy migration.
5-node cluster simulator on your laptop. Real consensus, real routing, chaos injection. Web dashboard with live metrics.
Production cluster. Same slices, different scale. Moving from Ember to Aether is a configuration change, not a code change.
Cluster setup, slice deployment, load testing — end to end.
Full runtime: consensus, QUIC, streaming, 4 cloud providers, mTLS, ML autoscaling, PostgreSQL driver — all in one 49MB JAR. Built with JBCT (Java Backend Coding Technology) — deterministic patterns optimized for human-AI collaboration.
You don't have to go all-in. Start with Aether Ember in a single JVM alongside your existing application. Extract one hot path, deploy as a slice, route traffic.
First slice running in Forge in under an hour.