3 ms·

So does this mean Apigee will be the captive API gateway for Google's extensive portfolio of APIs, or will the Apigee gateway still be offered as a product to p

by niftich 10y ago

So does this mean Apigee will be the captive API gateway for Google's extensive portfolio of APIs, or will the Apigee gateway still be offered as a product to put in front of a customer's custom API?

CrunchQL 10y ago
It makes no mention of using it on Google's APIs at all. Within the blog it elaborates on what they're doing by saying: > Google cloud customers are already benefitting from no sys-ops dev environments, including Google App Engine and Google Container Engine. Now, with Apigee’s API management platform, they'll be able to front these secure and scalable services with a simple way to provide the exported APIs. >As always, we'll make sure that these capabilities are available in the public clouds and can also be used on-premises. If you click on the link and read the article it will give information behind the headline, possibly answering questions the headline brings up.
- niftich 10y ago
  I appreciate the summary but I was speculating about things that weren't said (in the article). Specifically, as you point out, the article makes no statement on whether they will dogfood Apigee for internal use, but recently they acquired Firebase where dogfooding it was a part of the play. Meanwhile, there's these lines: > Google cloud customers are already benefitting from no sys-ops dev environments, including Google App Engine and Google Container Engine. Now, with Apigee’s API management platform, they'll be able to front these secure and scalable services with a simple way to provide the exported APIs. >As always, we'll make sure that these capabilities are available in the public clouds and can also be used on-premises. It unnecessarily combines two different things in the same sentence; "you can continue to rely on your stuff running in Google App Engine and Google Container Engine"; and "you can front your stuff with Apigee Edge" -- yes, I can already do both of these things today. So what's the difference?
nl 10y ago
I think that it doesn't make a lot of sense for Google to use Apigee on its own APIs. They seem to do a pretty decent job of scaling, monitoring and securing them on their own. What does make a lot of sense is a tool to give people who host on the Google cloud better control over who is using APIs they (the customers) produce. For example, you can imagine Apigee expanding to enable transparent scaling of (some) self-hosted APIs onto Google's cloud via intelligent caching.

by niftich 10y ago

So does this mean Apigee will be the captive API gateway for Google's extensive portfolio of APIs, or will the Apigee gateway still be offered as a product to put in front of a customer's custom API?

CrunchQL 10y ago

It makes no mention of using it on Google's APIs at all. Within the blog it elaborates on what they're doing by saying: > Google cloud customers are already benefitting from no sys-ops dev environments, including Google App Engine and Google Container Engine. Now, with Apigee’s API management platform, they'll be able to front these secure and scalable services with a simple way to provide the exported APIs. >As always, we'll make sure that these capabilities are available in the public clouds and can also be used on-premises. If you click on the link and read the article it will give information behind the headline, possibly answering questions the headline brings up.

niftich 10y ago
I appreciate the summary but I was speculating about things that weren't said (in the article). Specifically, as you point out, the article makes no statement on whether they will dogfood Apigee for internal use, but recently they acquired Firebase where dogfooding it was a part of the play. Meanwhile, there's these lines: > Google cloud customers are already benefitting from no sys-ops dev environments, including Google App Engine and Google Container Engine. Now, with Apigee’s API management platform, they'll be able to front these secure and scalable services with a simple way to provide the exported APIs. >As always, we'll make sure that these capabilities are available in the public clouds and can also be used on-premises. It unnecessarily combines two different things in the same sentence; "you can continue to rely on your stuff running in Google App Engine and Google Container Engine"; and "you can front your stuff with Apigee Edge" -- yes, I can already do both of these things today. So what's the difference?

nl 10y ago

I think that it doesn't make a lot of sense for Google to use Apigee on its own APIs. They seem to do a pretty decent job of scaling, monitoring and securing them on their own. What does make a lot of sense is a tool to give people who host on the Google cloud better control over who is using APIs they (the customers) produce. For example, you can imagine Apigee expanding to enable transparent scaling of (some) self-hosted APIs onto Google's cloud via intelligent caching.