The introduction of AI, automation and data storytelling to the world of analytics has not only had an immediate impact on the end users of analytics but also the people that work in the field. While many analysts may fear they will be replaced by automation and AI, CEO of Yellowfin, Glen Rabie, believes that the role of the data analyst will increase in significance to the business and breadth of skills required.
Many websites and even applications online are built on top of a CMS. According to recent survey data, WordPress has a 60% market share, making it the most popular CMS by far. The next closest competitor, Joomla, has only 5.2%! But unlike bespoke software, many people don’t test their WordPress website. While the core of WordPress is fairly well tested by it’s creators, users, and the open source community, the same cannot be said for every plugin and theme.
Let me start by saying I love proof of concepts (PoCs), especially when Splunk is involved. PoCs allow me to validate the technical feasibility of our platform with customers and remove any doubts about implementing the technology. While a PoC is an effective way for businesses to evaluate new technologies, you may encounter pitfalls if you’re not well prepared. If you want to give your PoC the best chance of success, it’s important to understand these common mistakes and how to avoid them.
jsDelivr, the first and only free multi-CDN for open source projects are now using PerfOps FlexBalancer to load balance between their sponsoring CDNs. Until now, jsDelivr had been using Cedexis Openmix to achieve its Multi-CDN load balancing. After analyzing the ease of migration and benefits of FlexBalancer, jsDelivr decided that it was time for a change.
So you want to A/B test your web app. The idea is simple, but the details can get messy, and you don’t want to re-invent the wheel. Services like Optimizely are pretty good, but they can be expensive and full of features you don’t need immediately. In this post, we’ll share how Sentry wrote an experimentation system with minimal work.
In the last post, Samuell (from the og-aws Slack group) figured out his negative TTL problems in Cloudfront. During that session, we actually solved two different problems. This post is to finish off that conversation and address the other problem, which was how to use the default error page in Cloudfront.
Developing modern, microservice-based applications can be challenging. When we launched Developer Mode last month, we were interested in seeing how providing a stream of structured trace data could make it easier to instrument and write applications.
Developing Artificial Intelligence and Machine Learning models comes with many challenges. One of those challenges is understanding why a model acts in a certain way. What’s really happening behind its ‘decision-making’ process? What causes unforeseen behavior in a model? To offer a suitable solution we must first understand the problem. Is it a bug in the code? A structural error within the model itself? Or, perhaps it’s a biased dataset?