In this series Microservices in the Real World, I’ve been sharing our journey to cloud native. First there was the challenge of automating memory management in our containerized Java application, then we had to secure our containers (thank you, Red Hat), and then we had to figure out how to run an application, which we started building before Kubernetes was a thing, on Kubernetes. Which puts us at “cloud native-ish.” The next question for us was: How do we fully automate our application lifecycle?
During and before re:Invent 2019, Amazon unveiled over 77 new product announcements and unique capabilities. AWS Compute Optimizer, one of the more interesting offerings was quietly announced through a blog on December 3rd.
This blog is part of a series in which we share some of the results from our 2019 State of Performance in Modern Applications Survey.
Prefer to binge read the results? Download the full report here.
There is an ongoing discussion (read:argument) around something that is like the Voldemort of technology: vendor lock-in.
This blog kicks off a series of blogs in which we share some of the results from our State of Performance in Modern Applications Survey.
Want to binge read the results? Download the full report here.
Last week approx. 65,000 IT professionals and executives converged on to Las Vegas for the most significant cloud event in the world: AWS re:Invent. It is hard to describe the spectacle, noise, excitement, and energy at the event.
Let me start by giving my one line view of the reason for the uprising in awareness of microservices, containers, SDN and the ever-present SDDC (Software-Defined Data Center): This is about agility, not speed.
We are continuously being confronted with challenge in designing infrastructure. Every aspect of our infrastructure has potential pitfalls for performance, resiliency, and the challenges faced with dynamic workloads.
Few people will argue that public clouds haven’t dramatically changed the industry in the past few years. There has been a tremendous increase in popularity of public cloud services such as Amazon AWS and Microsoft’s Azure, and the demand keeps growing every year. Concerns that prevented companies from choosing public clouds as their go to infrastructure, such as security, reliability, stability, quality assurance and more are becoming more manageable.
A recent blog post from VMware’s CTO office discusses "DRS Pairwise Balancing", an allegedly improved version of DRS in vSphere 6.5 and later. "This new feature", the blog proclaims, "is needed as clusters keep on growing larger and larger." Turns out that some statistical measures used by old DRS became "statistical outliers" in larger clusters, that according to VMware "simply disappear as noise due to the vast number of hosts that experience far lower utilization” and thus fall "below the threshold required to trigger load balancing.”