iwf
iWF is a Workflow-As-Code microservice orchestration platform offering an orchestration coding framework and service for building resilient, fault-tolerant, scalable long-running processes
Not yet testedsource: GitHubGoMITcommit ad3d109fd9d8
Go, MIT licensed. The project labels itself: distributed process, distributed system, distributed transactions, durable timer, golang, java, message queue and microservice.
iwf has not been verified yet.
Measured by Argusic on a fresh machine every time. Every number links to its evidence.
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
No recorded runs.
Topics (from GitHub)
distributed-processdistributed-systemdistributed-transactionsdurable-timergolangjavamessage-queuemicroserviceorchestrationorchestratorpersistenceprocesspythontimerworkflowworkflow-as-codeworkflow-engine
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/iwf)Questions
- Does iwf run?
- iwf has not been fully verified yet. No recorded run has produced a verdict yet.
- How did Argusic test iwf?
- On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
- Where is the evidence for iwf?
- All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.