The latest News and Information on API Development, Management, Monitoring, and related technologies.
Matt and I are out in Los Angeles this week for KubeCon 2021 this week. At the GitOpsCon event Tuesday we were excited to attend this Kubernetes session: GitOps in the Real World: Opportunities for Developer Experience Improvement.
As LogDNA has grown, many of our customers have too, meaning that they are bringing in more ingestion data sources and expanding their use cases for their logs. To help with managing more data, we’re excited to introduce the Control API suite. We’ve built 4 individual APIs that will help companies programmatically configure their data and how they want to ingest logs. Below, we’ll cover each new API in detail as well as why they are massively impactful for our customers.
Have you ever written a Hello, World! application? In most of these tutorials the first step is to log words to the console. It's an easy way to understand what is going on with your application and readily available in every programming language. The console output is incredibly powerful, and it has become easier than ever to capture that output as logs. As your application grows and evolves you need to implement a structured application log approach.
When embarking on digital transformation, success often comes down to using the right tools for the job. Emerging technologies have the ability to enable organizations to deliver better customer experiences more efficiently. This truism can serve as a forcing function for engineering teams to routinely reevaluate their tech choices and make sure they aren't missing out on a better solution.
The Query Data API is a Honeycomb Enterprise feature. With a Honeycomb Enterprise account, you can use this API today. Head over to our API docs to learn how to get access to your data. If you aren’t yet a Honeycomb Enterprise user, try it out by requesting an Enterprise Trial. Starting today, Honeycomb Enterprise customers can use the Honeycomb Query Data API to programmatically run queries and retrieve their results, and pull query results into any data visualization tool of their choice.
At Torq, we use gRPC as our one and only synchronous communication protocol. Microservices communicate with each other using gRPC, our external API is exposed via gRPC and our frontend application (written using VueJS) uses the gRPC protocol to communicate with our backend services. One of the main strengths of gRPC is the community and the language support. Given some proto files, you can generate a server and a client for most programming languages.
Within any enterprise, IT operations teams use a variety of solutions to monitor their technology ecosystem. These products are often business critical and cannot easily be replaced or migrated. Ultimately, it’s important that teams can analyze and correlate data from these different tools so they can produce the insights they need to improve decision making. To help address these requirements, Broadcom offers RESTMon.
Load testing isn’t an engineer’s favorite task. Every setup choice made during performance testing will yield varying results. The chosen load test protocol is the difference between an application that performs well under most circumstances and one that buckles at hidden stress points. Yet failing to run adequate tests isn’t an option when dealing with a complex API architecture. Needless to say, all your load testing options must be carefully evaluated.
You might already be using Splunk to manage your Salesforce environment with the help of the Splunk App for Salesforce and the Splunk Add-on for Salesforce that allows a Splunk administrator to collect different types of data from Salesforce using REST APIs. This solution is great and the events give you an idea of how users interact with Salesforce. These events can range from Apex executions to page views.
gRPC is an open-source Remote Procedure Call system focusing on high performance. There exist several gRPC benchmarks including an official one, yet we still wanted to create our own. Why would we torture ourselves doing such a thing? So with those points in mind, we created a completely open-source benchmark where everyone is welcome to contribute and which could be run with a single command, having only Docker as a prerequisite.
