Google didn't pay for the technology. Apigee has a good set of big enterprise customers that Google was missing on their cloud platform. As others mentioned, Google already have the tech: https://cloud.google.com/endpoints/
I misread that as "to acquire Apple". Then I misread that again as "to acquire Apogee" (as in, the name 3D Realms went by from 1987 to 1996).
Now I'm wondering behind the reasoning of the Apigee brand. Was it an intentional play on Apogee Software of the 80s/90s? If so, why? Something about "playing with APIs" I presume, but that seems confusing.
Apogee used to also be a compiler company, it's where the domain apogee.com has pointed as long as I can remember. They used to have a link to the shareware company iirc. Now it looks like they provide Java runtimes for embedded devices
Apigee is a pretty decent product if you are in the space. It's sort of kinda like a "CDN for APIs", if that make sense, which I've always thought is a great idea.
(Yes, I realize my analogy has limits. Don't get too hung up on it though)
I didn't realize they were a public company though.
I think this is an excellent acquisition by Google, specifically for their cloud platform. It provides an excellent solution to the problem of managing apis and a tight integration with cloud platform will really make it stand out.
These various "API management" services have always struck me as value subtracting as much as value adding. Adding another moving part to a system doesn't make it more reliable.
One thing that has amazed me is that most of these services offer everything but the kitchen sink AND the one thing you need for a minimum viable product, which is the ability to charge for API calls.
> A good API needs to [...] give developers the freedom to work in the development environment of their choice [...] a good API includes testing support
Those are two of the main reasons not to use Apigee.
My day job used 3scale. Actually it won out against apigee, mashery, and a few other big players. My day job liked a few others because they were associated to "big enterprise names" - especially since my day job is a big enterprise. I think 3scale were still kind of pricey, but way cheaper than the other big players...However, I give big kudos for 3scale support, especially during on-ramping.
The major acquisitions in this space already happened...
CA bought layer7. Mulesoft bought programmable web. Intel bought and divested mastery. Microsoft bought Apiphany.
The last one standing is Akana, (formerly SOA Software).
APIgee was always a weird company to go public - I think it makes sense for them to be part of google. More of a feature that belongs in some other cloud management stack.
Well. At first I thought this was crazy, but then I realized Google was the only major cloud provider that didn't offer an API Gateway service... Azure and AWS both have one.
So, makes sense. They got them cheap as well, only a really small premium of the stock price.
We use Apigee's Edge product. It provides API management tools like authentication, authorization, rate limiting, etc before the request hits your actual API. Its a pretty good product, if that isn't your core competency.
Is it just me, or should API management be done through GraphQL? It doesn't seem like Apigee even uses GraphQL (unless I missed something on their website). Been looking at GraphQL recently, and it looks like it could be a solution. Any experience on using GraphQL in a prod environment?
EDIT: I think Apigee has a great product, not wanting to put them down.
We moved our entire api to Apigee at my previous job (500+ person fast growing startup). It certainly has value and was a great fit for us. Many aspects of the Apigee stack felt kinda weird and cumbersome though and I saw such a huge potential for improvement if you started with GraphQL as the base assumption instead of REST. So that's what we are doing at https://graph.cool/ :-)
We are currently in closed beta, but I'd be happy to personally onboard you or chat if that would be helpful. (contact in profile)
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?
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.
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.
Apigee has a lot of smart engineers working on nodejs based open source projects and contributing to OpenApi spec (fka Swagger). Good to see that Chet K chose Google to acquire these talented engineers. And ofcourse the Apigee community is A++.
Hi firefoxNX11, it looks like you misspelled a link a year and a half ago and accidentally linked to a phishing site. You have been shadowbanned since, I saw you with showdead on. It looks like you have made constructive comments otherwise, perhaps a mod can help out!
Aw man I bought a bunch of these shares last year at $7 and sold for $7.90 after a few months. I was happy about it. Wish I held onto them, it's trading at $17 now!
[+] [-] msoad|9 years ago|reply
[+] [-] sinzone|9 years ago|reply
[+] [-] illicium|9 years ago|reply
[+] [-] unknown|9 years ago|reply
[deleted]
[+] [-] mathattack|9 years ago|reply
[+] [-] gizmodo59|9 years ago|reply
2020: We are now discontinuing Apigee.
[+] [-] pluma|9 years ago|reply
Now I'm wondering behind the reasoning of the Apigee brand. Was it an intentional play on Apogee Software of the 80s/90s? If so, why? Something about "playing with APIs" I presume, but that seems confusing.
[+] [-] randallsquared|9 years ago|reply
[+] [-] oldmanjay|9 years ago|reply
[+] [-] samfisher83|9 years ago|reply
[+] [-] bluedino|9 years ago|reply
[+] [-] nl|9 years ago|reply
It's a pretty decent name for an API gateway.
[+] [-] k-mcgrady|9 years ago|reply
[+] [-] knz|9 years ago|reply
[+] [-] nl|9 years ago|reply
(Yes, I realize my analogy has limits. Don't get too hung up on it though)
I didn't realize they were a public company though.
[+] [-] internal_tools|9 years ago|reply
[+] [-] PaulHoule|9 years ago|reply
One thing that has amazed me is that most of these services offer everything but the kitchen sink AND the one thing you need for a minimum viable product, which is the ability to charge for API calls.
[+] [-] antoncohen|9 years ago|reply
> A good API needs to [...] give developers the freedom to work in the development environment of their choice [...] a good API includes testing support
Those are two of the main reasons not to use Apigee.
[+] [-] ajainy|9 years ago|reply
API Gateways are big deal in API first initiatives.
[+] [-] niftich|9 years ago|reply
[1] https://techcrunch.com/2013/04/17/source-mashery-is-selling-... [2] https://techcrunch.com/2013/04/22/ca-acquires-layer-7-techno...
[+] [-] wing328hk|9 years ago|reply
[+] [-] mxuribe|9 years ago|reply
[+] [-] patwolf|9 years ago|reply
[+] [-] abakker|9 years ago|reply
CA bought layer7. Mulesoft bought programmable web. Intel bought and divested mastery. Microsoft bought Apiphany.
The last one standing is Akana, (formerly SOA Software).
APIgee was always a weird company to go public - I think it makes sense for them to be part of google. More of a feature that belongs in some other cloud management stack.
[+] [-] edwinnathaniel|9 years ago|reply
[+] [-] unknown|9 years ago|reply
[deleted]
[+] [-] tootie|9 years ago|reply
[+] [-] doppenhe|9 years ago|reply
[+] [-] theDoug|9 years ago|reply
Apigee is a different company and set of products.
[+] [-] j_s|9 years ago|reply
[+] [-] supergeek133|9 years ago|reply
So, makes sense. They got them cheap as well, only a really small premium of the stock price.
[+] [-] bduerst|9 years ago|reply
[+] [-] aikah|9 years ago|reply
[+] [-] kyork|9 years ago|reply
[+] [-] kelvin0|9 years ago|reply
EDIT: I think Apigee has a great product, not wanting to put them down.
[+] [-] sorenbs|9 years ago|reply
We are currently in closed beta, but I'd be happy to personally onboard you or chat if that would be helpful. (contact in profile)
[+] [-] olalonde|9 years ago|reply
Does that mean there's a chance Apigee will get open sourced? (fingers crossed)
[+] [-] ctdean|9 years ago|reply
[+] [-] cobookman|9 years ago|reply
[+] [-] unknown|9 years ago|reply
[deleted]
[+] [-] niftich|9 years ago|reply
[+] [-] nl|9 years ago|reply
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.
[+] [-] CrunchQL|9 years ago|reply
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.
[+] [-] yueq|9 years ago|reply
[+] [-] unknown|9 years ago|reply
[deleted]
[+] [-] firefoxNX11|9 years ago|reply
[+] [-] doublerebel|9 years ago|reply
[+] [-] hellofunk|9 years ago|reply
[+] [-] chatmasta|9 years ago|reply
[+] [-] komali2|9 years ago|reply