DevOps configuration management & automation
Your web application is not just a web application
Your web application is not just a web application. In fact your web application might rely on hundreds of other applications, databases, web servers, load balancers, fail-overs as well as virtual environments, physical hardware and multiple datacenters — not to mention the configurations that make everything work together.
“My ecommerce app is so binary and super easy to manage…
(said no one in the last 15 years.)”
Write a script. Get it done.
Back in the day a simple MSI was sufficient, but no longer. With today’s mixed Windows/ Linux environments, application, database and middleware interrelationships and complexities, it’s not so simple anymore. And there is so much at stake if even the tiniest typo finds its way into your script – namely performance problems, outages and security vulnerabilities. (See Barry’s cautionary tale).
True DevOps configuration management requires a more robust approach.
DevOps configuration management and automation: It’s about time
DevOps and configuration management and automation go hand in hand. And with the DevOps movement has come a ton of cultural change, innovation, and more tools than you can shake a stick at. (Yep, we’re from Texas). Many DevOps tools are focused on building, testing or deploying applications while others manage infrastructure or networks. But even with the growing list of new DevOps tool choices…
One glaring gap is the management and automation of application configurations and their middleware for both Windows and Linux.
Some infrastructure tools can handle the task for Linux and Unix environments, but Windows shops have been treated like an afterthought. What’s needed is a true DevOps Configuration Automation Solution for Linux and Windows.
Until Orca, there hasn’t been an application configuration automation solution that caters to the uniqueness of both Windows and Linux environments.
Why Developers love Orca:
- Set up your own Test environments
- Less frustration
- Standardization of repeatable processes
- Development of best practices
- Increase speed to market
- Better application quality
- Both Dev & Ops have access with assigned views and permissions to execute specific tasks.
- Dev doesn’t have to ask Ops for changes with detailed descriptions
Why IT Ops loves Orca:
- Change transparency between Dev and Ops
- Less involvement from Ops when Dev needs environments created
- Less overhead to track and manage large numbers of ecosystems
- Less time to locate and identify issues or failures
- Automated drift detection and remediation
- Increased stability
- Increased availability
- Increased visibility of application, database and middleware configs
- Visibility of app relationships and their ecosystems
- Granular reporting of the ‘who, what, when, and where’ of changes.