6 ms·
As someone who has spent the past two years delving into Kubernertes and other Docker orchestration platforms, the answer is currently... "not much". Kong does
by developer2 7y ago
As someone who has spent the past two years delving into Kubernertes and other Docker orchestration platforms, the answer is currently... "not much".
Kong does have a certain position in the industry (they are at least "known"), but their competition has done a better job taking market share. There are many API Gateways and Service Meshes trying to get their piece of the pie, and Kong has so far failed to be one of the true front runners. Products built on top of Envoy have so far done a better job of attracting users.
That isn't to say Kong can't try to assert themselves with another injection of cash. The industry is still very much up in arms, with all of us waiting for someone to step up and take over as the defacto gateway and/or mesh; preferably BOTH the gateway AND the mesh. Kubernetes itself is effectively the defacto standard, but the things you plug into it are certainly still in flux.
- Bombthecat 7y agoI'm curious, which other commercial product offers service mesh on kubernetes / in from of microservices? Axway,IBM,red hat etc are all monolotiths and to big / slow for microservices. Only other commercial firm I know of is crunch 42. And maybe you can count Salesforce api gateway.but they go a different way...
- SideburnsOfDoom 7y agoIf you're on AWS, they will push you towards the AWS things such as "Amazon API gateway", which does ... API Gateway things. Seems to be a similar case on Azure https://aws.amazon.com/api-gateway/ https://aws.amazon.com/api-gateway/ https://docs.microsoft.com/en-us/azure/architecture/microservices/design/gateway#choosing-a-gateway-technology https://docs.microsoft.com/en-us/azure/architecture/microser...
- Bombthecat 7y agoWhich is not a service mesh / micro service gateway...
- SideburnsOfDoom 7y agoI'm not following. First off, "service mesh" and "microservice" are not the same thing. There are plenty of microservice systems without a service mesh. Second, look at https://aws.amazon.com/api-gateway/ https://aws.amazon.com/api-gateway/ It talks about routing to EC2 - that's virtual machines in Autoscaling groups and load balancers, running web apis, your classic backend microservices. So this is a micro service gateway. Maybe it doesn't have the best pricing or features for your case, but it is a micro service gateway. Then goes on to the other services that it routes to: lambdas and bunch of other things, including containers in ECS. Is that service mesh? https://aws.amazon.com/blogs/compute/using-amazon-api-gateway-with-microservices-deployed-on-amazon-ecs/ https://aws.amazon.com/blogs/compute/using-amazon-api-gatewa... AWS now have a service mesh thing, which appears to be unconnected: https://aws.amazon.com/app-mesh/ https://aws.amazon.com/app-mesh/
- Bombthecat 7y agoTake a look here: https://github.com/Haufe-Lexware/wicked.haufe.io https://github.com/Haufe-Lexware/wicked.haufe.io This goes into the right direction how I think a service mesh / microservice / micro gateway architecture should look / what the software needs to offer.