This is part of a 3-part series on APIs, sustainability, and climate change. Check out part 1 on managing a greener API lifecycle, and part 2 on ways to embed and innovate on top of third-party APIs to make greener products. In this final part, we will look at the environmental impact of common architecture trends and recommend steps to take to minimize the impact of each.
Recently, I was fortunate to have an insightful conversation with Matt Klein, Lyft software engineer and creator of Envoy, the popular open-source edge and service proxy for cloud-native applications. Envoy was the third project to graduate from the Cloud Native Computing Foundation (CNCF), following Kubernetes and Prometheus. Before Lyft, Matt held positions at Microsoft, Amazon and Twitter, and served on the oversight committee and board of the CNCF.
In this Kongcast episode, Josh Long, Spring Developer Advocate at VMware, dives into how Spring changed the way developers build Java applications and introduces you to Spring Native. Check out the transcript and video from our conversation below, and be sure to subscribe to get email alerts for the latest new episodes.
TBC Bank is a technology-driven company in Georgia. We are happy to announce that we have chosen Kong to improve our API ecosystem and leverage its technological resources, expertise and international footprint to further simplify the daily lives of our users. TBC wanted to partner with a company that, in addition to providing the technology platform required to publish APIs in our bank, would also offer a strategy for developing and implementing API management principles.
This is the second part of our three-part blog series on APIs, sustainability and climate change. Missed the first part? Check it out here. In this blog, we examine ways to consume and embed APIs to make our own processes greener and show how APIs are the building blocks of a new wave of green innovation. The API economy – and therefore the ways we can use APIs to cut carbon emissions and make technology more sustainable – is not just about building APIs but consuming them too.
The proliferation of microservices has led to many new innovative approaches in the software world. However, building robust, quality APIs that consistently deliver the business outcomes you desire can be a complex task. It’s no wonder a recent survey of organizations adopting microservices found that nearly 30% of the respondents listed “API quality” as one of their biggest challenges. API-based applications don’t just come in one flavor.
The quest for resilience and agility has driven us into the modern age of microservices. Bringing services to market on a microservice architecture demands utilization of sprawling technology offerings and tooling. While daunting at first glance, we can break down the process into 3 major categories: In this hands on series, we will use.
The API management space is changing – fast. In the past couple of years alone, we’ve seen huge changes in the deployment patterns that our customers are adopting. In the past, when the use cases were fairly simple, organizations would deploy an API gateway as a SaaS monolith in the cloud, sitting at the edge of the network. They did this because it was the best option available at the time, and the first wave of API management vendors like Apigee had a solution that could support it.
I’ve just got off a call with one of the largest banks in Sweden, and my brain is racing with ideas. I need to get this down on paper. I want to drop everything I’m doing and spend the next week in that mental headspace where all you do is explore and live and breathe a topic, with occasional breaks for sleep, after which you race out of bed so you can go back to where you left off. You know what I mean. What’s got me so fired up? Climate change.
It’s not uncommon for organizations to have to deploy solutions across (or among) multiple security domains. Here, we use the term “security domain” to refer to a segregated network environment, like a restricted internal network or a DMZ. This post will explore some design considerations when deploying Kong Mesh (and Kuma, the CNCF-hosted open source project upon which Kong Mesh is built) in environments with multiple security domains.
