Until recently, applications were built using infrastructure components like SQL Databases, elastic search, file share and web servers which can be easily replicated in a developer’s local environment. Once the code is ready to be released, it is taken over by the operations team for deployment in a cloud environment. Access to the production cloud environment is provided strictly on a need basis and is largely limited to accessing logs, metrics and occasional runtime environment access for troubleshooting. Work responsibilities of application developers and operations team were clearly defined. …
Two major shifts are happening across all industries today:
As seen by the increased adoption of public clouds, most enterprises are beginning to move towards a cloud based infrastructure where deployments are 100% software driven and underlying resources are becoming quite standardized. In fact, most cloud vendors even have a very similar nomenclature for resources when it comes to their global infrastructure in terms of VMs, Networking and Volumes. On the other hand, applications are becoming a combination of micro-services using containers, managed…
The customer connected with DuploCloud while looking for DevOps expertise to bring in automation. As part of a successful POC, their processes were automated end-to-end, improving backup time from days to 15 minutes. DuploCloud then partnered with the company to implement a seamless migration to AWS using automation.
About the Client
Founded in 2006, our client manages Intellectual Property (IP) assets for large corporations. Innovation is at their core with a patent life cycle management system through which customers are able to unlock value from within their patent portfolio and identify a roadmap to further developing their IP portfolios.
Infrastructure-as-code (IaC) is a very well known and popular technology for cloud infrastructure provisioning using principles of application development i.e. writing code (a programming language). While IaC is emulating application development, the technology has several limitations in the way it is built and works. These make the operationalization of IaC at scale to be challenging. In this blog we will discuss the following:
While it is not possible to compete with a public cloud in terms of feature set, elasticity, scale, managed services, geographic reach and bursty workloads, there are cases where it makes sense to run part of the workloads in an on-premises environment. AWS recognizes the potential benefits of a hybrid requirement as detailed on their edge offering using AWS technologies called AWS Outposts (https://aws.amazon.com/outposts/). Microsoft with Azure stack has similar offerings where they provide an edge deployment using hardware and software managed by them.
In the context of this blog, we will refer to AWS Outpost synonymous to Azure stack
Gartner’s hype cycle for new technologies has proven accurate many times over, and cloud technologies are no different.
You’ll walk that same curve when introducing cloud and DevOps into your organization. You may start with inflated expectations, but then reality hits you, and you dip into the “trough of disillusionment.
Cloud compliance is one cause of such disillusionment — when the marketing claims of push-button infrastructure give way to delays after you find out what it takes to make your cloud infrastructure compliant.
Looking up from the bottom may make the ultimate goal seem too high to reach.
In the last two decades we have seen the emergence of new computing models, a new discipline called DevOps and a new way of packaging and deploying applications using containers. However, this new way of provisioning infrastructure and deploying applications has brought a new set of challenges that are putting a lot of burden on enterprise IT. Primarily, there is a proliferation of tools that IT needs to manage, operate and stitch together to handle these fast paced application development environments. …
As we are moving to cloud based infrastructure, more and more teams are looking to use some kind of Infrastructure-as-code solution. This allows them to keep all changes under a version control system and review infrastructure changes by a senior devops person before they are actually deployed.
While Infrastructure-as-code has its advantages, it also comes with its own set of challenges. Based on talking to VPs of engineering, CTOs and devops leaders, we have classified their problems into a few categories:
DuploCloud was engaged with its strategic customer, a world’s leading supply chain risk management platform, to migrate their decade old IT infrastructure with a few TBs of data from a private data center to the AWS and Azure cloud. Their hosting costs were reduced from north of $1,000,000 per year to $250,000. DuploCloud successfully completed this project with under 19 hours of effective downtime and three weeks of efficient agile planning and mock drills.
The infrastructure was setup more than a decade ago. At a high level there were 2 main challenges: