Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google and IBM announce Istio – easily secure and manage microservices

developer.ibm.com

Post reply on HN
Print view View original

111–120 of 123 posts

Re: Google and IBM announce Istio – easily secure and manage microservices

#111

Post by spullara »

einrealist wrote: post #77
rdli wrote: post #45

Earlier quoted context omitted.

Well said. Besides Netflix, I'd put Twitter as an early pioneer, with their work on Finagle. Both of these companies, for better or worse, took a library-centric approach (Eureka/Hystrix/etc or the Finagle lib). This limited their applicability to the JVM. The sidecar model that AirBnb pioneered with SmartStack, later adopted by Yelp and others was the cheapest way to get non-Java langs to have similar resilience/obs…

Maybe a local proxy, deployed with the service, is a good answer to my objections, rather than having a centralised approach. This can help in polyglot environments, but remove any limitations a centralised solution would impose. Something like Istio would be an agent a service connects to locally, used for service discovery, complex routing or rate limiting. The configuration is service specific. Load balancing is d…

Maybe you don't understand how Istio works. The Envoy proxy is locally deployed as a sidecar next to each process. The centralization is entirely for the control plane. The local proxy uses the centrally managed configuration for making local decisions about routing.

Re: Google and IBM announce Istio – easily secure and manage microservices

#112

Post by AmIFirstToThink »

gregbrail wrote: post #63
tyingq wrote: post #55

Earlier quoted context omitted.

That's an example of the breakage though. Apigee's cloud runs in only 2 specific AWS regions. So once you tie all these pieces together, you end up with a long path, with some functionality that should be closer to the end user.

Apigee's cloud runs in a lot more than two AWS regions today, not to mention GCP regions, and the whole product can be installed in your own datacenter. We also offer a "micro gateway" that lets the proxy component run anywhere and communicate with the rest of Apigee via an API. We'll be taking this hybrid mode further and the Istio integration is one of the things that will take advantage of that hybrid model. (I wo…

>the whole product can be installed in your own datacenter

Could you please provide a link to documentation/articles that showcase this use case... on-premise installation of Apigee?

Re: Google and IBM announce Istio – easily secure and manage microservices

#113

Post by goodroot »

tyingq wrote: post #3

Interesting, but there's currently a lot of overlap between competing things that want to inject themselves between service consumers and service producers. There's API gateway products (Apigee, Kong, etc). Load balancers and proxies of various types. Caching and CDN products. More niche stuff like bot blocking, and this attempt to bundle control and statistics. It would be nice if some sort of standard pattern emerg…

Disclaimer: I work with Fly.

We're building something a lot like that! https://fly.io

Currently, we support AWS Lambda, Heroku, and self-hosted backends. Bringing things to the edge can give some major benefits; a smart proxy, too, can give developers a lot of power with minimal effort.

Re: Google and IBM announce Istio – easily secure and manage microservices

#114

Post by graycat »

gegtik wrote: post #105
graycat wrote: post #99

Earlier quoted context omitted.

Nice. Thanks. I'm perfectly serious -- obviously the OP didn't define microservices -- you did. Good for you. Bad for the OP. Okay, microservices look like what used to be called agents . For their communications there have been various efforts at ways to define data objects , complete with a registration hierarchy (that is, a case of public naming) and an inheritance hierarchy (roughly like some of inheritance in so…

There's some reading here https://hn.algolia.com/?query=microservice&sort=byPopularity...

Good. Maybe the OP should have given the reference.

My main interest here is not microservices but just to tell the HN and computing community to be much more careful with undefined terminology and acronyms.

Here we now have some good descriptions and references on microservices. Good.

My main point is that articles on computing need to have, gee, call them links, to explain jargon and acronyms, to explain stuff not in an English dictionary. The OP on microservices I am using just as an example.

To me, poor technical writing in computing and computer documentation has been one of the worst obstacles to my startup -- darned near killed my startup -- and is a sore point.

Re: Google and IBM announce Istio – easily secure and manage microservices

#115

Post by akhimich »

AmIFirstToThink wrote: post #112
gregbrail wrote: post #63

Earlier quoted context omitted.

Apigee's cloud runs in a lot more than two AWS regions today, not to mention GCP regions, and the whole product can be installed in your own datacenter. We also offer a "micro gateway" that lets the proxy component run anywhere and communicate with the rest of Apigee via an API. We'll be taking this hybrid mode further and the Istio integration is one of the things that will take advantage of that hybrid model. (I wo…

>the whole product can be installed in your own datacenter Could you please provide a link to documentation/articles that showcase this use case... on-premise installation of Apigee?

Here is what i found http://docs.apigee.com/private-cloud/latest/overview

(I work at Apigee)

Re: Google and IBM announce Istio – easily secure and manage microservices

#116

Post by tannhaeuser »

parasubvert wrote: post #35
einrealist wrote: post #8

What happened to dumb pipes, smart endpoints? We do the same things again that we did before with SOA, having hard-to-replace middleware / bus systems.

The REST architecture always included the possibility of gateways and proxies in the end-to-end communication path to delegate shared responsibilities out of the user agent or origin server. This balances the need for centralized admin of some things and decentralized deployment of other things. Most microservices systems, even if they're not using HTTP in favor of something like gRPC, Kafka, or Rabbit, are taking a…

For me "SOA" doesn't imply "an ESB" in the way you seem to understand the term, and even though I've actually worked with Sonic MQ/ESB which brought the name to the scene, I still don't know what people really mean when speaking about "an ESB".

From a developer perspective, service-oriented just means that you're offering/accessing functionality via a well-defined app-specific network protocol interface with a standard taxonomy/representation of cross-cutting concerns such as auth, transactions/compensations, message synchronicity and QoS semantics (eg. request/response, at-least once delivery etc.), most of which define the shape of your service implementation code fundamentally. For example, if you're operating under the assumption that no distributed transactions are available, you'll have to fold the necessary logic for restarting and state management into your application code.

Re: Google and IBM announce Istio – easily secure and manage microservices

#118

Post by tyingq »

gregbrail wrote: post #63
tyingq wrote: post #55

Earlier quoted context omitted.

That's an example of the breakage though. Apigee's cloud runs in only 2 specific AWS regions. So once you tie all these pieces together, you end up with a long path, with some functionality that should be closer to the end user.

Apigee's cloud runs in a lot more than two AWS regions today, not to mention GCP regions, and the whole product can be installed in your own datacenter. We also offer a "micro gateway" that lets the proxy component run anywhere and communicate with the rest of Apigee via an API. We'll be taking this hybrid mode further and the Istio integration is one of the things that will take advantage of that hybrid model. (I wo…

Sorry, yes. I should have said only two of the four US regions.

Re: Google and IBM announce Istio – easily secure and manage microservices

#119

Post by graphememes »

graycat wrote: post #99
graphememes wrote: post #90

Earlier quoted context omitted.

I'm not sure if you're trolling or genuinely don't understand, so I think I can help you a little bit. Microservices are services that are generally containerized and are easily distributable through some form of a network to be easily replaceable parts. These services are defined by a specification where they do a single task, expose some endpoint or API and are composable with other microservices. There is a need f…

Nice. Thanks. I'm perfectly serious -- obviously the OP didn't define microservices -- you did. Good for you. Bad for the OP. Okay, microservices look like what used to be called agents . For their communications there have been various efforts at ways to define data objects , complete with a registration hierarchy (that is, a case of public naming) and an inheritance hierarchy (roughly like some of inheritance in so…

Sounds like you've got a good grasp on learning terms and acronyms already. Glad to see that the Wikipedia article helped ;)

Re: Google and IBM announce Istio – easily secure and manage microservices

#120

Post by grays »

spullara wrote: post #107
Spearchucker wrote: post #96

Earlier quoted context omitted.

I agree with your point about layer 3 networking being unable to easily tackle these problems. I question though, whther Istio is "all that". Securing an endpoint without requiring changes within the endpoint has been done for some time - Whale Communications, which became Unified Access Gateway, F5 Big IP, IBM DataPower... They are called web application firewalls, and unless I'm missing something Istio is no more t…

You are missing experience working in an environment with endpoint scale. You can't configure the O(N^2) paths between application instances changing every hour with those kinds of systems.

More information here: https://istio.io/blog/istio-auth-for-microservices.html
Post reply on HN