Drop us a line

Myths

MYTH #1 We offer an automatic tool; be brave, do it yourself…

    • Reality: One has to hire highly skilled coders with proficiency in obscure languages and development tools to write and maintain automation code. Many vendors mask requirements for an SDK and heavy programming using shiny show cases. The truth is, it’s still a tremendous undertaking for any enterprise and defies the notion of a truly automatic experience. A Chef and Puppet paradigm…
    • Unity: Eliminates the need for coding, replacing it with a purpose-built software optimized for personnel who deploy, manage and build applications. Provides flexible visual templates with intelligent orchestration and minimal customization requirements.

 

MYTH #2 We do 100% automation; just need pre-packaged VMs to clone “components”…

    • Reality: A cumbersome semi-automatic process that leads to huge image libraries and never-ending proves of configuration and maintenance across data centers and cloud infrastructure providers. Every new component, new version of a component, new OS patch or OS version contributes to exponential complexity (100s and 1000s of images). This approach does not scale operationally and will bury any IT team. Cliqr anyone?
    • Unity: Moves the burden of creating and managing image libraries from people to the system itself. If desired, the system can auto-generate VM or Docker images on the fly from the same visual template, in any data center and on any cloud. No costly and slow replication, no hassle, no upgrade nightmares.

 

MYTH #3 We offer Templates, Blueprints…. We have them, “sort of…”

    • Reality: Do you think converting command line calls of a cloud OS or a workflow engine to a configuration file format makes a TEMPLATE or BLUEPRINT? Would tying together resource allocation with software configuration and run it as a script does the justice? Hitchcock couldn’t come up with a better horror story…  Instead of coding in a procedural language, one has to code in a complex, domain specific language without any means to troubleshoot. It is still the code… But wait; in addition to learning how to code the application configuration flow, one has to learn coding for OpenStack, Amazon, Chef, Puppet…, ugh, I’m out of here!
    • Unity: Unity Templates actually hide cloud APIs. Templates are visually composed through guided user interactions. They truly unite infrastructure and application orchestration. Unity does the heavy lifting and shields users from complexity.

 

MYTH #4 Global Scale? Sure, we can scale…, “well it depends…”

    • Reality: Even simple applications require HA/DR configurations running across data centers and cloud OS providers; shifting loads based on needs. Existing tools cannot operate effectively in this environment – it again falls back on people to do the heavy lifting. Not-so-open-and-laborious OpenStack…
    • Unity: Embraces multi-location, multi-cloud deployments as standard. Orchestrates at scale in one data center or across many. One click provisions application environments in any cloud OS at any location. And yes, no people are necessary to push images around or manually drive global deployment.