Developer Relations is not simply a role or department at API-first companies. Developer relations is a mindset of getting developers adopt a platform and making them successful with their initiatives rather than attempting to sell to those developers. This makes developer relations different from traditional sales and marketing roles.
With increasing popularity among API Gateways, which provides authentication, rate-limiting and access control between applications that expose their APIs and the consumer of the APIs are the bedrock of API infrastructure. Simple architecture which bundles API related functionality inside a single component provides load balancing, caching and ability to scale to ensure high availability.
For more than 70 years, EBSCO has supported research at private and public institutions, including libraries, universities, hospitals, and government organizations. One of the reasons that customers have continued to rely upon us over the decades is because we actively innovate and adapt new technologies to give customers access to the growing pool of digital resources in the information age.
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.
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!
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?”
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.
