{"id":29063,"date":"2018-11-14T17:26:58","date_gmt":"2018-11-14T15:26:58","guid":{"rendered":"http:\/\/arcadsoftware.com\/?p=29063"},"modified":"2022-12-05T18:11:04","modified_gmt":"2022-12-05T16:11:04","slug":"arcad-software-launches-pay-per-use-system-for-drops-their-flagship-application-release-orchestration-aro-solution","status":"publish","type":"post","link":"https:\/\/www.arcadsoftware.com\/arcad\/news-events\/arcad-press-articles\/arcad-software-launches-pay-per-use-system-for-drops-their-flagship-application-release-orchestration-aro-solution\/","title":{"rendered":"ARCAD Software launches “Pay-per-Use” system for DROPS, their flagship Application Release Orchestration (ARO) solution"},"content":{"rendered":"

Annecy, France and Peterborough, NH, USA – 12 November 2018<\/strong>\u00a0\u2013 ARCAD Software, market leader in Enterprise DevOps and Modernization solutions, today announced the launch of a new Pay-per-Use pricing system for DROPS, their flagship Application Release Orchestration solution.<\/p>\n

<\/p>\n

The new “metered” pricing model brings DROPS within the reach of smaller development shops, and offers a low entry cost for mid- to large-size enterprises.\u00a0 Though DROPS is well-established as an enterprise-grade solution, this move follows the company strategy of making \u201cDevOps affordable for everyone\u201d.<\/p>\n

Pay-per-Use drives the scalability of DROPS in line with modern hybrid infrastructures.\u00a0 DROPS users can now purchase sets of deployment units, each unit corresponding to a deployment action.\u00a0 Licenses are consumed as deployments are executed, and additional deployment capacity is downloadable on demand from ARCAD\u2019s self-service portal.\u00a0 Tech support and remote consultancy services are bundled with pay-per-use DROPS licenses.<\/p>\n

At the current time, the new pricing model is supported for distributed systems Windows, Linux, UNIX, and the payment mode will be extended to ARCAD\u2019s customers on IBM i (aka iSeries, AS\/400) and mainframe z\/OS in a later release.\u00a0 In parallel, ARCAD Software will continue to support the more traditional system of permanent licenses per “infrastructure item” (deployment target) leaving free choice open to its customers.<\/p>\n

Pay-per-Use = Pay-as-you-Deploy<\/h3>\n

Marc Dallas, R&D Director at ARCAD Software, explained the rationale behind the new payment system:<\/p>\n

\u00ab\u00a0We have introduced the DROPS Pay-per-Use model to simplify the deployment process, and in particular the budgeting and cross charging<\/em> for application deployment.\u00a0 In today\u2019s cloud environments where containers are rapidly spun up on demand by Dev and QA teams, deployment targets are often transient, so predicting the number of infrastructure items required to cover future deployment needs is a challenge in itself.\u00a0 In general, teams find it easier to estimate the actual number of deployments they will perform and now they can license DROPS accordingly.\u00a0 By pricing the solution by deployment action rather than target, budget forecasts become more accurate and controllable.\u00a0 And by moving to a “metered” payment system our customers are sure they only pay for what they really need\u00a0\u00bb.<\/p>\n

Multi-platform and Legacy Support<\/h3>\n

DROPS already has a unique position in the market from its universal multi-platform support and in particular its optional, advanced features for legacy systems such as IBM i (aka iSeries, AS\/400) and mainframe z\/OS.\u00a0 Now to meet customer requirements, ARCAD is also leading in the areas of “DevOps for Data” and DevSecOps, i.e. security demands when deploying into enterprise application estates.<\/p>\n

Containerization and “DevOps for Data”<\/h3>\n

A common characteristic of modern environments is the use of container platforms, such as Docker.\u00a0 One of the strengths of containers lies in allowing the rapid provisioning of target environments early in the development cycle, to enable the “Dev” area of the IT Delivery ecosystem to rapidly test changes before transferring to production.<\/p>\n

While extremely powerful, containerization must be handled with care.\u00a0\u00a0 Best practices in the use of containers dictate that data volumes are managed separately, to ensure the persistence and consistency of data when a container is spun down or deleted.\u00a0 This modularity is achieved using microservices.\u00a0 In practice this rule is often bypassed and some implementations loosely combine binaries and data in the same container.<\/p>\n

ARCAD\u2019s DROPS rapidly solves this problem with DROPS-Datachanger, an integrated “DevOps for Data” system, which manages both changes in data but most importantly also any changes in database structure to secure the integrity of target environments. DROPS-Datachanger delivers:<\/p>\n