Live data from Hacker News

Google and IBM announce Istio – easily secure and manage microservices

developer.ibm.com

121–123 of 123 posts

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

#121
post #105

Earlier quoted context omitted.

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 no…

I guess my point is that microservices have been well trodden in this forum context, I would not expect every article to require a basic primer explaining every concept

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

#123

Earlier quoted context omitted.

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 standa…

SOA doesnt have to imply an ESB, true, but it usually did in practice. I too worked with Sonic , IBM broker, Mule, but mostly BEA WebLogic and AquaLogic. What was often missing in popular SOA was services-oriented delivery, where the unit of deployment was independently evolvabke from others. It was more focused on interface modularity for some future implementation decomposition of the monolith. It fulfilled half the problem.

Microservices have been enabling a new generation to accomplish this decomposition through by focusing on services oriented delivery and deployment, and by dramatically constraining the protocols to HTTP, maybe some pub/sub or gRPC, not likely many others (and thus no distributed transactions, simpler QoS levels, etc).

Post reply on HN