The latest News and Information on APIs, Mobile, AI, Machine Learning, IoT, Open Source and more!
Katie Schmidt, senior manager of AI/machine learning user experience research, contributed to this blog. Years of user experience (UX) research and customer feedback have shown that building trust is integral to success with AI. With generative AI (GenAI), trust is more important than ever.
Organizations — particularly those with high security and compliance requirements — need a customizable way to explore and innovate with artificial intelligence and other new technologies. This is why we’re happy to introduce OpenOps, an open source platform designed to help organizations experiment with AI in a secure environment they control. OpenOps is a framework of several tools that enables you to test open source AI models in a sandbox.
The Kubernetes networking landscape is shifting. The traditional Kubernetes Ingress approach is being complemented and, in some cases, replaced by a more powerful, flexible, and extensible standard: the Kubernetes Gateway API. Kubernetes has become the go-to platform for orchestrating and managing containerized applications. A key aspect of Kubernetes that's crucial for the functionality of these applications? Networking.
Earlier this week we shared some exciting news. Checkly has made its mark in not one, but two Gartner Hype Cycles reports. We're being recognized for something we're super passionate about - Monitoring as Code (MaC). This recognition comes in the Hype Cycle for Monitoring and Observability and the first ever Hype Cycle for Site Reliability Engineering. It's a big deal for us, and here's why it should matter to you, too.
In the previous blog in this series, we delved into the redesigned architecture of Amazon Prime Video and how they integrated different architectural styles for optimal performance and cost efficiency. We also discussed the impact of Amazon’s decision on the concept of a “serverless-first” mindset, highlighting the importance of considering alternative architectural approaches based on specific use cases and requirements.
I’ve been a firmware engineer at two wearable companies in the past, Pebble and Fitbit, and there was always one class of customer support tickets and user complaints that never went away: issues around battery life. It was a constant game of whack-a-mole with every new firmware version introducing a battery regression.
