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.
Navigating the transition from monolith to microservices can be an ambitious undertaking for any organization. Today, we’re launching our new Kong GTM Partner Program to create a global ecosystem of experts to help organizations successfully transition to microservices, service mesh and other modern architectures. We’re rolling out the program with 20 inaugural members worldwide, including value-added resellers (VARs) and systems integrators (SIs), that have been carefully selected and qualified.
Uptime Robot provided 2 api-key types: a master api_key and monitor-specific api_key. The master api_key can be used to perform almost every action exists in the dashboard and it must not be revealed for the security of the accounts.
Over the last year or so, I experimented with different ways of getting customer feedback for Checkly. This post is about what worked for us and how I was totally wrong about chat widgets.
Starting the migration from monolith to microservices can be daunting. Still more daunting is to have spent a couple years on it and still not understand “what done looks like.” If you have an ORM-based monolith, there’s a strong temptation to do a data-first migration: to move a model or set of models into a CRUD service and then call it using HTTP instead of the database.
ReadyAPI just got a brand-new update for 2019, and it is BIG. We've added a ton of enhancements to the ReadyAPI tools in 2.7 and even added support for one of the most popular technologies in software today: GraphQL. So, let's get started and talk about the big things you'll get with an upgrade to ReadyAPI 2.7: