IT teams face many visibility challenges due to the massive shift to remote work due to the Coronavirus outbreak. This includes the variability of home network environments, reliance on SaaS and cloud applications, the unpredictability of Internet transport, and higher congestion than ever before. How do you overcome these monitoring challenges?
Ten years ago, Amazon found that every 100ms of latency would cost them roughly 1% in sales. This is a pretty clear statement on the importance of user experience! It’s especially true in today’s ultra-competitive market where the cost of switching (to another provider) for consumers is lower than ever. And one of the most common performance issues in serverless architectures is related to elevated latencies from services we depend on.
How do you design a product that customers love to hate? “Hey, that thing you’re responsible for is down. Oh, and people have noticed and they’re complaining about you on Twitter. OK BYEEE!” Our customers love PagerDuty (they legit tell us this). At the same time, they hate hearing from us because it means trouble.
It comes as no surprise that the demand for Kubernetes is skyrocketing across the industry. According to the CNCF’s 2019 survey, 78% of respondents are using Kubernetes in production today. This growth is contributing to a surge of demand for talent: there are over 100 thousand cloud native job postings across Dice and Indeed alone. The talent pool of people that have worked with Kubernetes and the adjacent technologies is limited and demand is growing.
We’re pleased to introduce you to the latest Elastic Cloud features and functionality. Grab a cup of your favorite beverage and five minutes, and let’s dive in.
When Kibana 4.0 was created back in 2015, it only had three apps: Dashboard, Visualize, and Discover. Fast forward five years, Kibana now consists of 100+ plugins, millions of lines of code, thousands of dependencies, and dozens of frameworks. The architecture of Kibana that worked well with three apps had become a bottleneck that was hindering Kibana’s stability, scalability, performance, and development velocity.
The first HashiConf Digital event was held on June 22-24, online. The event was meant to be HashiConf Amsterdam, but the team pivoted and moved it online because of COVID-19. My employer FireHydrant was a sponsor, and I was happy to have a chance to attend. The event was very well organized, and that’s even more impressive given that the team had to shift it online.