fabcode
| Crates.io | fabcode |
| lib.rs | fabcode |
| version | 0.2.0 |
| source | src |
| created_at | 2022-08-20 13:21:46.893137 |
| updated_at | 2022-08-21 18:11:01.056153 |
| description | FabCode sets out to build GUI based workflow engine that will help speed up development. |
| homepage | https://fabcode.xyz |
| repository | https://github.com/fabcode-xyz/fabcode |
| max_upload_size | |
| id | 649334 |
| size | 6,671 |
Satyender Yadav (hckkid)
documentation
README
Introduction
(WIP) FabCode is set to provide GUI based programming of business logic for building cloud native services. Later to be extended to allow building edge applications too. Development of FabCode is to consist of few core layers.
- FabCode DSL
- FabCode GUI
- FabCode Adapters
- FabCode Schedule
- FabCode Monitor
- FabCode Orchestrate
- FabCode Tracer
- FabCode Audit
Usage
Work in progress, to be updated as project develops
FabCode DSL
FabCode DSL will be a DSL & its interpreter + type checker. This DSL will allow describing a workflow / state machine which represents target business logic. DSL will support elements like conditions, loops, function calls. DSL can provide bounded time execution given no recursion or recursion with bound variant. DSL will have optional metadata to be used for help with rendering on GUI layer, this metadata can be kept totally separate. Long term outlook of FabCode is to allow Saga pattern & Microservice Architecture.
FabCode GUI
FabCode GUI will target a look very similar to UE Blueprint. This will be used on top of FabCode DSL and used to write business logic.
FabCode Adapters
FabCode will allow adapters, for example HTTP Fetch Adapter can be made to make API calls, this way functionality or business logic that is not written in FabCode remains accessible to FabCode. A generic way is to be also provided to write Custom Adapters, so any end usage can be achieved.
FabCode Schedule
FabCode Schedule will allow writing of recurrent Logic basis either a trigger or time based policy.
FabCode Monitor
FabCode Monitor is to provide a way to assess resource consumption, usage and failure / success rates of logic written.
FabCode Orchestrate
FabCode Orchestrate is to provide an orchestration layer to auto scale up and down resources required to serve business logic at desired load.
FabCode Tracer
FabCode tracer is going to allow distributed tracing cross business logic written in FabCode ecosystem.
FabCode Audit
FabCode Audit module will be the optional provenance layer to allow Audit of Data Change happening through FabCode.