Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resurrecting Celluloid by digital mortal combat. #1

Open
4 tasks
digitalextremist opened this issue Mar 25, 2020 · 0 comments
Open
4 tasks

Resurrecting Celluloid by digital mortal combat. #1

digitalextremist opened this issue Mar 25, 2020 · 0 comments

Comments

@digitalextremist
Copy link

Per celluloid/celluloid#789

We need a reference implementation. Why not a monster?

Rather than expect people of every language to migrate to Ruby ( and later Crystal ) to be able to use Celluloid, a standalone system can be programmed using Celluloid, which then tests other systems. I doesn't matter if there are already such systems, like with HTTP/S servers themselves, before Reel was created. The point is, Celluloid has its own special ways to unleash hell.

  • Execute parallel attacks of randomized patterns on multiple networks of endpoints.
  • Generate payloads to hurl at un/suspecting systems, in various extensible formats.
  • Stay on and furious; mercilessly attack an entire development environment for days.
  • Adds to Test Design by allowing people to write .monster specs of what to crush.

If we can blast systems to death, we can feel much more confident they will stand under fire. And the level of battle hardening needed now is too extreme to leave to chance. This type of mortal combat for information systems is badly needed in a way Celluloid is uniquely able to provide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant