FAQs
Frequently asked questions
Section titled “Frequently asked questions”Find answers to the most common questions about Fluxzero. Can’t find what you’re looking for? Join our community or open an issue.
Getting Started
Section titled “Getting Started”What is Fluxzero and how is it different from traditional frameworks?
Fluxzero is a cloud designed for the AI era. It gives every product a reliable backend and eliminates infrastructure complexity through a message-driven programming model. Instead of you or your agent writing REST controllers, repositories, and service layers, the application contains message handlers focused on product behavior.
Traditional frameworks leave the application team responsible for HTTP routing, database connections, message queues, and service configuration. Fluxzero handles all of this automatically, letting you focus on your product’s behavior.
Do I need to be a developer to build with Fluxzero?
No. The easiest way to start is to copy one instruction into your coding agent. You decide what the product should do, while the agent works in the application code and Fluxzero handles the backend foundation.
The result is a real Java or Kotlin codebase, not a generated black box. Developers can inspect, test, and extend it directly in their own IDE, and builders who do not want to write code can keep working through their agent.
Do I need to learn event sourcing to use Fluxzero?
No. While Fluxzero supports event sourcing as the default persistence strategy for aggregates, you don’t need to understand event sourcing to get started. You can begin by writing simple message handlers and gradually learn more advanced patterns as needed.
Event sourcing is just one of many patterns available in Fluxzero. You can also use document-based storage for simpler use cases.
What programming languages does Fluxzero support?
Fluxzero application code is currently written in Java or Kotlin. Your coding agent can write that code using the existing JVM libraries and tools.
We chose Java/Kotlin because they provide excellent tooling, type safety, and a mature ecosystem that works well with enterprise development.
Is Fluxzero suitable for small projects or just enterprise applications?
Fluxzero works great for projects of any size. Small projects benefit from faster development and simpler testing, while large projects benefit from built-in scalability and maintainability.
The productivity gains are often most noticeable in small to medium projects where you don’t have dedicated DevOps resources.
Technical Architecture
Section titled “Technical Architecture”How does Fluxzero handle database management?
Fluxzero abstracts away database complexity completely. You don’t write SQL queries, manage connections, or handle transactions manually.
For aggregates, Fluxzero uses event sourcing by default, storing events in an optimized format. For other data, you can use document-based storage with automatic indexing and search capabilities.
All persistence is handled transparently by the platform.
What happens to my HTTP endpoints? Do I still have REST APIs?
Yes, you still have HTTP endpoints, but you don’t write REST controllers and you do not expose an HTTP server in your application. Instead, you write message handlers, and Fluxzero automatically exposes them as HTTP endpoints through the fluxzero-proxy based on a few annotations.
How does Fluxzero handle scaling and performance?
Fluxzero is designed to scale horizontally out of the box:
- Automatic load balancing: Messages are distributed across instances
- Built-in backpressure: System handles load spikes without manual configuration
- Optimized storage: Event store and document storage are optimized for high throughput
You can scale by simply running more instances of your application.
Can I use external databases or am I locked into Fluxzero’s storage?
Fluxzero uses PostgreSQL as its underlying database, which you can not access directly. However, the platform is designed so you never have to write custom SQL.
For integrations with existing databases, you can use message handlers to read from or write to external systems while keeping your core business logic in Fluxzero’s managed storage.
How does message routing and delivery work?
Fluxzero uses consistent hashing to route messages to specific segments based on routing keys (usually entity IDs). This ensures:
- Messages for the same entity are always processed by the same consumer instance
- Related operations maintain strict ordering
- Load is distributed evenly across all instances
- The system can scale without repartitioning data
Building & Testing
Section titled “Building & Testing”Can I use my existing Java libraries and frameworks?
Yes! Fluxzero runs on the JVM and is compatible with most Java libraries. Typically you won’t need any libraries unless you have specific needs.
Can I debug my application like a normal Java application?
Yes! Since Fluxzero applications are regular JVM applications, you can use any Java debugger, profiler, or monitoring tool. Set breakpoints in your message handlers and debug normally.
The message-driven architecture actually makes debugging in production easier because you can trace the flow of messages through your application.
Deployment & Operations
Section titled “Deployment & Operations”How do I deploy Fluxzero applications to production?
See deployment chapter.
What monitoring and observability features are available?
Fluxzero provides comprehensive observability out of the box:
- Message tracing: Every message is tracked through the system
- Performance metrics: Built-in metrics for throughput, latency, and errors
- Health checks: Automatic health endpoints for load balancers
- Audit logs: Complete audit trail of all messages and state changes
How does Fluxzero handle database migrations and schema changes?
Since Fluxzero manages your database schema automatically, you don’t need to write database migrations. The platform handles schema evolution transparently.
When you change your message or aggregate structures, we provide best practises for versioning your messages to ensure backward compatibility.
Migration & Comparison
Section titled “Migration & Comparison”How does Fluxzero compare to Spring Boot?
While Spring Boot provides a framework for building applications, Fluxzero provides a complete platform that eliminates infrastructure concerns:
Spring Boot: You write controllers, services, repositories, and configuration
Fluxzero: You write message handlers with business logic only
Spring Boot: You manage databases, message queues, HTTP routing
Fluxzero: Platform handles all infrastructure automatically
Fluxzero is more opinionated but eliminates much more complexity.
Can I migrate an existing Spring Boot application to Fluxzero?
Yes, but it requires rethinking your architecture. Instead of migrating code directly, you typically:
- Identify your business operations (what your controllers do)
- Convert these to commands, queries, and events
- Rewrite business logic as message handlers
- Remove all infrastructure code (controllers, repositories, configurations)
The business logic stays the same, but the infrastructure layer is completely replaced.
How does Fluxzero compare to serverless platforms like AWS Lambda?
Fluxzero and serverless solve different problems:
Serverless: Great for event-driven functions but requires managing infrastructure between functions
Fluxzero: Provides a complete cloud with managed state and message routing
Fluxzero gives you a serverless-like building experience focused on product logic, but with managed state and message routing for complex applications.
Is vendor lock-in a concern with Fluxzero?
Fluxzero is open source, so you can always self-host or fork the project. Your business logic is written in standard Java/Kotlin without proprietary APIs.
The main dependency is on Fluxzero’s message-driven programming model. While this requires some rework to migrate away, your business logic remains portable since it’s just Java code.
© 2026 Fluxzero