skills.rest
3sy11
3sy11COMMUNITY
Explore all skills by this author →
GitHub

bollydog-framework

Build distributed async microservices with command-driven architecture and TOML configuration.

Updated Jun 28, 2024
Search Tags:#architecture#framework#async#protocols#command-pattern#microservice#hub
One-click install
npx skills add https://github.com/3sy11/bollydog --skill bollydog-framework
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bollydog-framework
Source: https://github.com/3sy11/bollydog/tree/main/docs
Command: npx skills add https://github.com/3sy11/bollydog --skill bollydog-framework

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bollydog Framework addresses the complexity of building scalable, distributed async microservices by providing a cohesive command-driven architecture that unifies entrypoints and runtime orchestration.

Core Features & Use Cases

  • Command as executable units and orchestration via Hub
  • Unified entrypoints across CLI, HTTP, WebSocket, and UDS
  • Protocol-based persistence and per-request context isolation
  • Zero-YAML startup with TOML configuration and dynamic service loading
  • Observability via tracing (OpenTelemetry) and lifecycle management

Quick Start

Install Bollydog, configure a minimal AppService and a Hello command, and run the framework to execute the command.

Frequently Asked Questions about bollydog-framework

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build scalable async microservices with a command-driven architecture?▼

You build scalable async microservices by implementing a thin command layer for executable units and orchestrating them via a central Hub, ensuring deterministic execution and observable tracing across distributed services.

What is the best way to unify CLI, HTTP, WebSocket, and UDS entrypoints in a microservice framework?▼

Unifying CLI, HTTP, WebSocket, and UDS entrypoints is achieved through a cohesive command-driven architecture that routes diverse protocols into a central Hub for consistent runtime orchestration.

How does command-driven orchestration work for distributed async microservices?▼

Command-driven orchestration works by enforcing a thin command layer that executes units of work, while a central Hub manages runtime orchestration, protocol-based persistence, and per-request context isolation.

Do I need YAML to configure async microservice frameworks, or can I use TOML?▼

You do not need YAML; this architecture supports zero-YAML startup by using TOML-based configuration and dynamic service loading to initialize distributed async microservices.

Can I use OpenTelemetry tracing for observability in async microservice architectures?▼

Yes, OpenTelemetry tracing is integrated directly into the architecture to provide end-to-end observability, lifecycle management, and deterministic execution tracing across distributed services.

When should I use a central Hub for microservice orchestration instead of direct service-to-service communication?▼

Use a central Hub for orchestration when you need to unify multiple entrypoints, enforce protocol-based persistence, and maintain per-request context isolation across distributed async microservices.

Related Skills

Explore More Software Engineering Skills→
KrastanovKrastanov
30

julia-toml

Parse and write TOML data in Julia using the standard TOML library.

Community
Basic
sheawinklersheawinkler
78

parallel-cli

Automate vendor web research and enrichment tasks via parallel-cli CLI workflows.

Community
Advanced
wshobsonwshobson
38.6k

service-mesh-observability

Implement distributed tracing and metrics collection for Istio and Linkerd service meshes.

Community
Advanced
roanbrasilroanbrasil
5

service-mesh

Configure Istio and Linkerd service meshes for mTLS, traffic splitting, and tracing.

Community
Advanced