Last month we released our new dashboards feature. Now’s a good time to drive your story with a dashboard of your own. Easily create with drag-and-drop - Clearly illustrate key metrics - Securely share between teams and partners
More and more companies are shifting from a traditional enterprise sales mindset to a developer-first mindset for driving product adoption. Sales calls and demos will not work as developers do not want to be sold to. Instead, the platform needs to be adopted similar to how consumers may adopt a mobile game or e-commerce app. Yet, developers are also less receptive to facebook ads that may have worked for those games and e-commerce apps.
Let’s admit it – web services (SOAP) are here to stay for a few more years, and maybe for a long time in some places where there is no business incentive to rebuild them. However, with a decline in new SOAP web services and most applications moving to cloud native architectures, a common query is “how can we support legacy services while moving to microservices?”
It has been a week since several of our mVISE and elastic.io developers attended the Vodafone TOBi Hackathon at the Vodafone Sky Lounge in Düsseldorf. Some of them were in the 3rd place team and all contributed greatly to the future success of the TOBi Chatbot. Teams formed, ideas flowed, problems were overcome, and the air was filled with the sounds of developer’s keystrokes!
By employing API analytics platforms Customer Success Management (CSM) teams can proactively help customers reach their goals, which in turn encourages them to renew their subscription and upgrade their contract. Getting your customers to love you is snap with customer-centric API analytics: integrations will happen faster, support will be more on-point and you’ll be set-up to provide real ongoing value.
Today, countless engineering teams have leveraged API monitoring to track infrastructure health and report when services are down or unhealthy. There are a variety of API metrics that can be tracked that are aligned with engineering goals such as uptime, average latency, requests per minute, and errors per minute. However, these metrics are not aligned with the business goals of product owners and growth teams.
We are happy to announce the release of Kuma 0.4! This is a major release focused on significantly better observability capabilities that also includes many new features and improvements across the board. This release also marks the 10th release of Kuma since September 2019!
Since its release in 2015, GraphQL has become the alternative to REST. It gives frontend developers the flexibility they craved for so long. Over are the days of begging backend developers for one-purpose-endpoints. Now a query can define all the data that is needed and request it in one go, cutting latency down by quite a bit, at least in theory. With REST, things were entirely a bit simpler — especially monitoring.
