Today Avi Networks and Red Hat spelled out the details of their collaboration to help enterprises develop and deploy production-ready microservices applications. The announcement comes on the eve of the Red Hat Summit in Boston. The joint solution with the Avi Vantage Platform providing container networking services for applications built on Red Hat Openshift will be demonstrated at the conference.
Ranga Rajagopalan, CTO at Avi Networks, recently published an article on Data Center Knowledge where he discusses how operations teams can become more agile in their development methodologies and manage east-west traffic more effectively.
Traditionally, applications were built as giant pieces of monolithic technology that were deployed on a single appliance and managed by a single IT team.
If you have been following the evolution of microservices architectures and container-based applications, you have also heard ample references to the need for visibility.
We were at MesosCon 2016 in Denver couple of weeks ago, and we will be at DockerCon and VelocityConf in Seattle and Santa Clara next week. Aside from bringing together the cognoscenti of container-based microservices, these events are serving a critical need.
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.
We are one weekend away from OpenStack Summit! As I pack my bags, I was thinking back to the previous summits I attended in Tokyo, Vancouver, and Paris. The community, the projects and the stability thereof, have evolved beyond everyone’s expectations and to the naysayers’ disbelief.
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.
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.