As a developer I would like to have built in
'dev'-swarm capabilities in the framework to quickly test run my app,
especially if I haven't learnt the magic of TDD yet.
The dev-swarm must provide an interface similar to dat-sdk that is easy to
boot. myStack.swarmOn('topic')
The built-in swarm should be easily disposable when I package my app, in case
i want to let a daemon provide the swarm capabilities or swarming is
abstracted and specifically handled by something else.
The dev-swarm should provide a helper for tests using mininet.
How can we make it intuitive? ( Why would we want to do this? )
The dev-swarm maybe could include "easy to spin up" swarm-configuration
scenarios, to maybe give us a baseline to test our rule-sets against.
I have many times wished that I had an easy way of replicating certain
connectivity scenarios in my test-environment, since some nasty bugs have only
been found while cabal was swarming.
Is there any merit to the idea or just a waste of time?
This is a task that I don't want to distract myself with right
now.
If anyone besides me happens to read this,
then feedback is always welcome (and so is implementation )
The dev-swarm must provide an interface similar to dat-sdk that is easy to boot.
myStack.swarmOn('topic')The built-in swarm should be easily disposable when I package my app, in case i want to let a daemon provide the swarm capabilities or swarming is abstracted and specifically handled by something else.
The dev-swarm should provide a helper for tests using mininet. How can we make it intuitive? ( Why would we want to do this? )
The dev-swarm maybe could include "easy to spin up" swarm-configuration scenarios, to maybe give us a baseline to test our rule-sets against.
I have many times wished that I had an easy way of replicating certain connectivity scenarios in my test-environment, since some nasty bugs have only been found while cabal was swarming.
Is there any merit to the idea or just a waste of time?