Today, we are excited to announce the release of Kong 1.3! Our engineering team and awesome community has contributed numerous features and improvements to this release. Based on the success of the 1.2 release, Kong 1.3 is the first version of Kong that natively supports gRPC proxying, upstream mutual TLS authentication, along with a bunch of new features and performance improvements.
This is part three in a series discussing the metrics pipeline powering Kong Cloud. In previous posts in this series, we’ve discussed how Kong Cloud collects, ships, and stores high volumes of metrics and time-series data. We’ve described the difference between push and pull models of collecting metrics data, and looked at the benefits and drawbacks of each from a manageability and performance perspective.
Apigee is great at managing your existing APIs – but how can you bring new technologies into your Apigee suite that lack an appropriate API? As it happens, DreamFactory is perfectly suited to creating a REST API fast for whatever datasource you need, and it can now be plugged straight into Apigee.
Apigee is great at managing your existing APIs – but how can you bring new technologies into your Apigee suite that lack an appropriate API? As it happens, DreamFactory is perfectly suited to creating a REST API fast for whatever datasource you need, and it can now be plugged straight into Apigee.
By the September deadline, Europe’s banks and fintech companies should be compliant with the Second Payment Services Directive (PSD2). Rather than focusing inwards on business operations, PSD2 is an outward-looking directive. It encourages open access and competition in the banking industry. Organisations across the breadth of the industry are required to open their payments infrastructures and customer data to third parties.
When a data breach occurs involving a cloud service, the impulsive reaction is to denounce using the cloud (at least for sensitive information). Since cloud security is not widely understood, it may be difficult to delineate it in the context of more general information security.
These days, companies are overflowing in data and tolerating ancient API-integrations. Across all industries. Buried in that data are trends that point to customer insights, inefficiencies and synergy opportunities that could provide a competitive edge to a company. Or, just help a company catch back up to its competitive peers. But how to best harness this data?
These days, companies are overflowing in data and tolerating ancient API-integrations. Across all industries. Buried in that data are trends that point to customer insights, inefficiencies and synergy opportunities that could provide a competitive edge to a company. Or, just help a company catch back up to its competitive peers. But how to best harness this data?
As APIs become the de facto standard for building and connecting business-critical applications, it’s important for operations teams to gain visibility into the security attributes of your APIs in order to continuously monitor and maintain the health of your API programs.
In the current microservices DevOps environment, there are tough new and evolving challenges for developers and teams to consider on top of the more traditional ones. From worsening versions of already common threats to new-generation evolving threats, new perspectives are required on securing microservices. These new perspectives may not be intuitive for many otherwise sophisticated DevOps and data teams.
