Dev Loves Open Source
Like so many other areas of enterprise software, when it comes to configuration and release management, many developers naturally gravitate to open source options.
It’s no wonder that 90% of code in modern applications is open source – after all, open source provides developers with…
Just Google it!
Don’t reinvent! Find out what others have done. And it’s
Ops needs Speed, Scale, Stability, Support & Security
But while Dev is drawn to prebuilt open source components that they can then modify, Ops has completely different needs
Great that it works in Dev and Test. I need it to work everywhere, all the time. And we need to add 10s of thousands of servers with no new resources.
Don’t force me to rebuild my infrastructure to be stable in a production environment.
Someone, somewhere needs to be on the hook for this software, with enforceable SLAs.
Failure is not an option. Our financial future and reputation is on the line.
- “One out of every 16 downloads of open source component requests are for a component with a known vulnerability.”*
- “31% of companies have had or suspect a breach in an open source component. Gaining control over open source risks is essential to improving security.”*
Out-of-the-box speed for quick time to market and low total cost of ownership.
My company is considering implementing (or has just implemented) an open source configuration management tool. That’s great for Dev. But as far as I can tell my job, and my team’s job, is about to get a LOT harder.VP IT Operations
In the context of configuration and release automation, can we satisfy both Dev and Ops?
Yes! Here’s why.
New application configuration automation solutions like Orca have recently launched. These solutions cater to Ops’ need for fully supported, central, secure control, ecosystem visibility, workflow automation and compliance enforcement – all at enterprise scale and without relying on open source, community driven scripts.
But what about Dev?
As a next generation DevOps solution, Orca provides Dev with application-centric modeling (after all it is all about the application), templated workflows (immediate gratification) and versioned full stack configurations (time and money savings) while providing accountable, knowledgeable support.