image
Akan.js
English
DocsConventionsReferencesCheatsheet
image
Akan.js
DocsConventionsReferencesCheatsheet
Released under the MIT License
Official Akan.js Consulting onAkansoft
Copyright © 2026 Akan.js All rights reserved.
System managed bybassman
General
• Authorization
• Schema Design
• Edge Computing
• File Management
• Single Sign-On
• DataList & Enum
Interface
• CRUD
• Endpoint
• Form
Observability
• Logging
• Dependency Injection
• Error Handling
• Metrics
Performance
• Caching
• Image Optimization
• Lazy Loading
• Querying
• Queueing
• Realtime
Development
• Documentation
• Script
• Docker
• Kubernetes
General
• Authorization
• Schema Design
• Edge Computing
• File Management
• Single Sign-On
• DataList & Enum
Interface
• CRUD
• Endpoint
• Form
Observability
• Logging
• Dependency Injection
• Error Handling
• Metrics
Performance
• Caching
• Image Optimization
• Lazy Loading
• Querying
• Queueing
• Realtime
Development
• Documentation
• Script
• Docker
• Kubernetes
Previous
Schema Design
Next
File Management

Edge Computing

Edge computing in Akan means this: one Akan server can call another Akan server with the same generated `fetch` object you already use in the app.
  • Cloud server: decides what should happen.
  • Edge server: does work close to the device or user.
  • Akan fetch: connects both sides with typed signal calls.

Call Another Server

The important part is the last option: `{ url }`. It tells fetch which server should receive the signal call.
Ping an edge server

Send Commands

Use normal query or mutation calls when the cloud wants the edge server to do something. The call still has typed arguments and typed return values.
Remote command

Listen To Status

Use subscriptions when the edge server keeps sending status. Save the unsubscribe function so you can clean up later.
Subscribe and cleanup

Wrap A Remote Node

When you talk to the same edge server many times, make a small class that remembers the URL and unsubscribe functions.
Small wrapper

Very Fast Data

Keep Akan fetch for commands and status. If you need huge video or binary streams, you can add another transport just for that data.
  • Commands: `fetch.startJob(...)`
  • Status: `fetch.subscribeJobStatus(...)`
  • Large streams: use a dedicated path only when needed.

Tips

  • Start with a normal signal. If it works locally, it can usually be called remotely by changing `{ url }`.
  • Keep edge server URLs in the database so cloud logic can loop over them.
  • Always clean up subscriptions. Long-running workers can leak connections otherwise.
Edge Computing
Call Another Server
Send Commands
Listen To Status
Wrap A Remote Node
Very Fast Data
Tips