Function Mesh: Function Driven Design

The Design Evolution We Need

Function Mesh: Function Driven Design bridges this gap using pure java.util.Function with configuration-driven metadata and zero learning curve. The solution isn't better deployment tools - those already exist. What we need is a development methodology that puts functions first.

See the Difference in Action

Function Mesh transforms traditional distributed programming by making remote function calls work like local dependency injection:

@Component
public class OrderProcessorFunction implements Function<CreateOrderRequest, OrderResult> {

    // Function Mesh automatically creates HTTP proxies for these!
    @RemoteFunction(name = "priceCalculator")
    private Function<OrderRequest, PriceInfo> priceCalculator;

    @Override
    public OrderResult apply(CreateOrderRequest request) {
        // Pure business logic - no HTTP, no URLs, no framework clutter
        PriceInfo priceInfo = priceCalculator.apply(request);

        String orderId = "order-" + System.currentTimeMillis();
        return OrderResult.success(orderId, priceInfo.getTotalPrice(),
                                 "Order processed successfully!");
    }
}

Help Improve Function Mesh

Function Mesh: Function Driven Design is more than a framework—it's an idea to make distributed programming better. We're building a community of developers who believe that distributed systems should be about writing better business logic, not managing infrastructure complexity.

Areas where we need contributors:

• Framework Adapters: Quarkus, Micronaut, and other JVM frameworks
• Cloud Adapters: Google Cloud Functions, Azure Functions, and other serverless platforms
• Enhanced Features: Service discovery, circuit breakers, and advanced security patterns
• Documentation & Examples: Real-world use cases and best practices
• Performance Optimization: Cold start improvements and runtime optimizations

Why This Approach Matters

Function Mesh: Function Driven Design addresses a fundamental gap in modern application development. Current FaaS platforms are deployment engines, not development frameworks. They excel at running and scaling functions but provide little support for the actual development experience.

This approach represents the next evolution in distributed development, where:

• Infrastructure becomes truly invisible - no HTTP clients, no URL management, no service discovery code
• Business logic stays pure - functions focus solely on business rules and domain logic
• Developer experience improves dramatically - familiar patterns, type safety, and standard testing approaches
• Portability increases - same code works across local development and any cloud provider
• Team productivity accelerates - less time on plumbing, more time on value creation