In the two previous posts in this series, we’ve explained cloud migration using the analogy of moving to a new home. The analogy presents applications as personal belongings and infrastructure as the properties you’re moving between.
Enterprises must undergo a digital transformation. It is not a matter of if, but when. And most IT organizations are choosing now as the time.
What are “Elastic Application Services”?
Last year, Ranga Rajagopalan, our CTO wrote a very informational post on “Application Services 101” that has been referenced in many prospect/customer discussions ever since! If you haven’t read the post, I highly recommend you do.
Webscale organizations such as Facebook, Google, and other large cloud vendors have modernized their infrastructure with open source software and commodity hardware. Bringing such a Webscale IT approach to mainstream enterprises was hard because they lacked the tools for such a transformation.
Organizations are adopting an app-centric approach to computing in their data centers and clouds. Microservices architectures are increasingly used by app-centric enterprises to achieve continuous development and delivery, scaling, and isolation through independent services. While microservices applications offer several advantages compared to monolithic applications, challenges with supporting application services remain.
This article originally appeared in Dark Reading on Apr 15, 2016.
The advantages offered by the container model go against many of the assumptions of traditional security mechanisms. Here are 5 new concepts & 4 best practices you'll need to understand.
Applications have become the lifeblood for businesses to generate revenue and stay competitive. It is not surprising that organizations are adopting an app-centric approach in their data centers and clouds. Microservices architectures enable continuous development and delivery, scaling, and isolation through independent services. While microservices applications offer several advantages compared to monolithic or even n-tier applications, appliance-based ADCs are not cost effective or in most cases, even viable to support the vast amount of east-west interactions between the services and provide no visibility to the application components. Developers need two common requirements: (a) they need flexibility and programmability to develop, test and deploy their apps quickly (b) they need visibility into application interactions and performance to pinpoint services that are at fault or to troubleshoot an application outage.
Traditional applications were built as static monoliths that were deployed and managed by IT. When a new application had to be deployed, IT would create a DNS entry for the application, allocate a virtual IP (VIP) and configure that VIP on a load balancer for the application to be discovered by other clients. In the best case scenario, this process took about 4-6 weeks. Enterprises have collectively recognized the inefficiencies in this throw-over-wall deployment hand-off of the application from developers to IT operations. There were no alternatives to this model in a data center dominated by purpose-built appliances owned by IT.