Fitz Framework Lets WASM Components Call Server Functions Without Manual API Wiring

·1 views

Fitz, a web framework, introduces an @rpc decorator that allows developers to mark server-side async functions and call them directly from WebAssembly client components as if they were local calls. The compiler automatically generates both the server-side HTTP endpoint (POST /__rpc/function_name) and a client-side fetch stub, eliminating the need to write routes, JSON glue code, or duplicate type definitions. A single shared type defined in the server module is compiled into both a native struct for the backend and a WASM struct for the frontend, preventing type drift between the two sides. The approach draws comparison to existing solutions like Next.js Server Actions, tRPC, and Phoenix, but requires no external dependencies, code generators, or special directives beyond the single decorator. This feature is presented as Part 7 of the ongoing FitzLiveViews series, building on earlier work covering server-rendered and WebSocket-based component compilation.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Fitz Framework Lets WASM Components Call Server Functions Without HTTP Boilerplate

Fitz, a full-stack web framework, introduces an @rpc decorator that automatically generates both a server-side HTTP endpoint and a client-side fetch stub from a single async function declaration. Developers can call server logic directly from a WebAssembly component as if it were a local function, using standard await syntax, with no hand-written HTTP handlers, fetch calls, or JSON parsing required. The same type definition is compiled for both the server and the WASM client, eliminating type drift between front and back ends. This is the seventh installment in a series documenting Fitz's component model, and the feature draws conceptual parallels to server actions in Next.js, tRPC, and Remix. The framework handles serialization, routing, and async state updates automatically, requiring no external dependencies beyond the built-in HTTP stack.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Open-Source AgentJIT Compiles AI Agent Workflows from 30s LLM Chains to 0.1ms Python

A developer has open-sourced AgentJIT, a just-in-time compiler designed to eliminate latency and cost inefficiencies in AI agent workflows. The tool works by tracing an agent's tool-call sequence on its first run and compiling the resulting execution path into a deterministic Python AST pipeline for all subsequent runs. This approach reduces multi-step LLM chain execution times from up to 45 seconds down to under 0.1 milliseconds, with no token costs on compiled runs. The compiler automatically inserts runtime input guards that trigger a fallback to the original LLM agent if unexpected inputs are detected, preventing crashes or regressions. AgentJIT is available as a self-contained Python library with no mandatory external dependencies and can be applied via simple decorators.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Oracle Autonomous AI Database 26ai Merges AI, Analytics, and Vector Search in One Platform

Oracle's Autonomous AI Database 26ai is a converged database platform designed to handle relational data, JSON, graph, spatial data, and vector embeddings within a single system. The platform aims to eliminate the complexity of managing multiple specialized tools by combining database storage, machine learning, analytics, and application development capabilities together. A key feature is its autonomous operation, which automates routine administrative tasks such as patching, backups, and performance monitoring, reducing the need for dedicated database administrators. Oracle AI Vector Search, another highlight of the platform, enables semantic similarity searches using numerical embeddings rather than exact keyword matching, powering technologies like Retrieval-Augmented Generation and enterprise knowledge search. The platform targets organizations looking to adopt AI solutions without building and maintaining complex multi-technology architectures.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Design a User Management System Using JWTs, Ktor, and Exposed

A developer tutorial from the Vesper Design Diaries series explains the critical distinctions between identity, authentication, and authorization in app development. Identity refers to who the user actually is, typically represented by a stable value like an email address, while authentication is the process of verifying that claim through passwords, OTPs, or biometrics. Authorization, by contrast, governs what a verified user is permitted to do within the system. The article argues that conflating these three concepts causes problems when apps need to support multiple login methods, role-based access, or account suspension without deletion. The series uses Kotlin Multiplatform app Vesper as a practical case study for implementing a production-grade user management system on a limited budget.

0 comments Read more at DEV Community