Welcome!

Plutora Brings DevOps to the Enterprise

Plutora Blog

Subscribe to Plutora Blog: eMailAlertsEmail Alerts
Get Plutora Blog via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Plutora Blog

Tailoring Release Management to Both Operations and Development Instead of adopting cookie-cutter solutions for release management based on static, flowchart-driven models, enterprises need purpose-built systems designed with a model that can be adapted to the needs of an individual enterprise that incorporate components from emerging DevOps-focused approaches to release management and more standard ITSM-focused approaches to IT Service Management. Your developers have their own dedicated tools and your operations team has its own dedicated IT service management tools. However, you still leave release managers to bridge the gap between these two sides of the release process without dedicated tools. It would be nice if there was a one-size-fits-all solution to release management, but there isn’t. In the latest Plutora whitepaper, Release Management Is Not a “One Size ... (more)

Continuous Delivery and Legacy Software | @DevOpsSummit #DevOps #Microservices

The future of software releases is clear. Continuous delivery is here to stay. But does that mean that legacy software systems and infrastructure need to be altogether abandoned? If you polled the people busy redefining best practices today, they'd agree that in a decade we're going to be effortlessly collaborating on highly complex systems that are updated continuously. QA will be fully automated, deployment and infrastructure tasks will be immediate, and large enterprise-wide software projects will be able to move quickly. In the future, software releases won't feel so "manual... (more)

Complexity at Scale: Trials and Tribulations of Success By @DaliborSiroky | @DevOpsSummit #DevOps

"Complexity" is often viewed as a negative. This is perhaps even more the case at scale, where some degree of complexity is unavoidable. Any unnecessary complexity, states the conventional wisdom, is public enemy number one. But does that wisdom ring true? Let's look a little closer at the contours and implications of complexity at scale. We're trained to avoid complexity when we design systems, and call systems with poor architecture "too complex." If you've worked in any large IT organization you understand the constant daily struggle against complexity at scale. Every day tea... (more)

Efficient Enterprise DevOps | @DevOpsSummit #DevOps #Microservices

Three Steps to Efficient Enterprise DevOps By Dalibor Siroky If you work for a large company, you'll often look around and wonder if moving to a daily release cycle or automating deployments is even possible given the number of meetings and the amount of process your releases are subject to. Between the CAB meetings, the QA schedules, and the coordinated conference calls it's tough to imagine a monthly release process being condensed down to a process that could run in a single day.  For most organizations dealing with real risk - it's true - you will not be able to condense rel... (more)

I Thought DevOps Integration Was Supposed to Be Easy By @DaliborSiroky | @DevOpsSummit #DevOps

I Thought DevOps Integration Was Supposed to Be Easy By Dalibor Siroky We've said it on this blog before, and we'll repeat the same message: Solving a software engineering problem is simple physics. It takes a set amount of energy to move a project from point A to point B, and changing the process or path doesn't change the unavoidable fact that difficult software problems are difficult to solve. DevOps integration is no different. If you have a complex, highly-orchestrated release no amount of automation can change the fact that the large, successful systems found in the Fortune ... (more)