pikku-concepts

Pikku maps common backend patterns to a function-centric model using a core pikkuFunc. This approach separates business logic from network protocols, enabling transport-agnostic routing, middleware, and validation across HTTP, WebSocket, queues, and RPC.

To wire a TypeScript function to HTTP and WebSocket, you map a core pikkuFunc to the desired transports. The function-centric model handles routing, middleware, and dependency injection, exposing the same business logic across multiple network protocols.

Dependency injection in a function-centric backend framework works by passing required services and data directly into the core function wire. This allows transport-agnostic business logic to access necessary dependencies uniformly across HTTP, WebSocket, queues, and RPC.

Yes, existing backend patterns like middleware and auth work with function-centric wiring. The framework maps these traditional patterns, along with validation and dependency injection, directly to its core functions for HTTP, WebSocket, and queues.

A TypeScript function-centric backend requires a project structure that separates core pikkuFunc definitions from transport configurations. This organization supports code generation, testing, and the mapping of services, data, and wire to HTTP, WebSocket, and queues.

Migrating an existing backend to a function-centric architecture involves mapping traditional routing, middleware, and validation patterns to core pikkuFunc definitions. This refactors existing logic into transport-agnostic functions wired to HTTP, WebSocket, queues, and RPC.