How kainsk/sdk works
Main Components
a) Core Components:
• Graph Database Layer
• State Function Runtime
• NATS Integration Layer
• Plugin System
• Cache System
• Monitoring/Metrics System
b) External Dependencies:
• NATS JetStream
• NATS Key-Value Store
• JavaScript V8 Engine
┌─ Application Layer ─────────────────────┐
• (User Applications) │
• Runtime Layer ──────────────────────────┤
• State Functions │
• Plugin System (JS) │
• Cache Management │
• Graph Database Layer ──────────────────┤
• CRUD Operations │
• JPGQL Query Engine │
• Transaction Management │
• Storage & Message Layer ───────────────┤
• NATS JetStream │
• NATS KV Store │
• ┘
Key Elements to Highlight
a) Graph Database Features:
• CRUD operations (embedded/graph/crud)
• JPGQL query engine (embedded/graph/jpgql)
• Transaction management (embedded/graph/tx)
• Debug capabilities (embedded/graph/debug)
b) Runtime Features:
• State function management (statefun/runtime.go)
• Cache system (statefun/cache)
• Plugin architecture (statefun/plugins)
c) Integration Points:
• NATS integration (embedded/nats)
• JavaScript plugin support (statefun/plugins/js)
• Monitoring/metrics (statefun/system)
Notes for Implementation
• Use clear boundaries between different layers
• Scaling points and distributed nature
• Version/configuration management
• Demonstrate error handling flow
• Monitoring/observability paths
• Distributed nature of the graph database
• Plugin extensibility
• State function runtime
• Integration with NATS ecosystem
• Monitoring capabilities