Operations#

So you've built something and now you need to keep it alive. This section is about the unsexy but absolutely necessary work of running Adama in production -- deploying your code, watching it breathe, and making sure nobody gets into rooms they shouldn't be in.

Chapters#

1. Deployment#

Getting Adama running for real. System requirements, configuration, the Solo server for when you just want one process and minimal fuss, space management, and the deployment workflow that lets you push changes without losing sleep. I walk through going from "it works on my machine" to "it works on the actual machine."

2. Monitoring#

Knowing what your deployment is actually doing. Health checks, metrics, logging, debugging techniques, and performance monitoring. The goal here is to see problems before your users tell you about them (because they will tell you, and it won't be pleasant).

3. Security#

Keeping things locked down. Authentication, compile-time privacy enforcement, policies, secure configuration, and the patterns I keep coming back to. Adama's security story starts at the language level -- the compiler catches privacy bugs before your code ever runs -- and that's genuinely one of my favorite things about the system.

Deployment Options#

You have choices for how to run this thing:

Solo Server#

Solo is a single-process deployment. One JVM, one process, everything bundled together. It's ideal for:

• Development and testing
• Single-tenant applications
• Edge computing scenarios
• Simple production deployments

Solo compiles Adama files from a directory and serves them immediately. No ceremony.

Cloud Deployment#

For multi-tenant, high-availability situations where you need the real infrastructure:

• Managed hosting
• Automatic scaling
• Global distribution
• Professional support

Operations Philosophy#

I designed Adama to be operationally boring. That's a compliment.

Minimal Moving Parts#

Traditional real-time applications need databases, caching layers, message queues, and application servers all talking to each other. Adama consolidates these into a single runtime. Fewer components means fewer things that can break at 3am.

Observable by Default#

Every deployment exposes health check endpoints and supports metrics collection. You don't need to instrument your code -- observability is baked in.

Security as Foundation#

Privacy and access control aren't operational concerns in Adama -- they're language features. The compiler enforces security policies before your code ever runs in production. This is a fundamentally different approach, and it means a whole class of "oops" simply can't happen.

Getting Started#

If you're deploying for the first time, start with Deployment to understand your options and get a server running.

If you already have Adama running and want better visibility into what it's doing, jump to Monitoring.

If you're preparing for a security review or just want to sleep better at night, Security covers both Adama-specific patterns and general best practices.