About REVVOPS
For REVVOPS performance is built into the name; the portmanteau of revving and DevOps that labels our
work. We're engineering cloud infrastructure software first,
because it's more challenging to genericise for widespread use than other kinds of cloud applications.
"Cloud infrastructure complexity is now exceeding cloud application complexity by a big margin and a new
approach is needed quickly" - as a Senior Solutions Architect at a leading cloud provider recently told us in person,
at one of their big conferences. As well as being cloud native,
all our software runs native as well, as you'll come to see when you try it.
In the technology industry, words and phrases such as performance, performant, high performance,
fast, faster, the fastest, lightning fast, light weight and other combinations thereof, are used loosely for promotional purposes
and usually with no explanation in support of any purported claims.
For REVVOPS performance has a definite explanation - it means software product
technology that's been compiled, optimized and created to run as native OS binary code without the use of
interpreted scripts, virtual machine bytecode interpretation and the like - an approach that
when done well scores highly in all metrics used to measure software
performance, not to mention the additional benefits of increased application stability, increased application
security and reduced configuration management burden.
REVVOPS V7 was based on Terraform, with the REVVOPS CLI originally designed to augment a large number of our own
modules.
REVVOPS V8 is based on the open source Pulumi IaC platform and does not make use of domain
specific languages (DSLs), proprietary or otherwise. The REVVOPS V8 Core can be supplied with all source code and training
options to further any customization needs, but the EP (enterprise production) binaries contain so much configurability you are unlikely to
require modifications to the source. The V8 Core source code does however make a great
educational resource for those interested in learning non DSL dependent IaC
programming techniques.