Skip to main content

FutureNET18 有感

這時的不是滋味可能就像20年前的SDH老傢伙一樣
service mesh也許才是王道

"Traditional networking has done a horrible job at monitoring and diagnostics."
The LinkedIn networking team is ~30 people. Which begs the question: how many people will be specialised in in networking in the years ahead.
“Service mesh is fashionable, it’s this season’s short black dress.” — Comment from at

Network issues are more complex in cloud native/ than traditional networking. Observability is key for and

I think organisations are too scared to start their microservices journey. But like anything else, it's baby steps - gradual change. You have to start somewhere with time, comes success.

Mastercard has been looking at Service Mesh as a method to extend cloud-native capability while keeping security top of the priority list. Service Mesh helps ensure the identity of service and the requestor.

It strikes me that the fashion for Service Mesh removes the need for cloud NFV. (NFV is, like, so yesterday and Service Mesh is so hot right now)

NFV is so 5 years ago. Service mesh takes the application centric view. It's networking according to the application folks gospel. NFV is just so overly complicated.

Traditional Sdn + service mesh - L7 SDN L7 SDN requires a management platform.

A recurring theme is that we all deal with monolithic applications that we can't or won't touch. Re-platforming isn't an option. We have to go to a higher level of abstraction.

3 industry trends to understand the journey of API Managment. Trend 1: Data is in motion Trend 2: microservices: Trend 3: Run Apications Anytime, Anywhere.

I hope you aren’t bored by service mesh’s yet because leaders in networking can’t talk about anything else. At , 4 of 5 presentations so far have been about service mesh.

At a "network" conference. We've talked Blockchain and Service Mesh. Future of Networking indeed.

180ms latency for Mastercard transactions with security embedded into the architecture.
API or Service management enters the equation. How does API or Service Management help to scale the technology to provide business value? IE how do you get Netflix scale out of your monolithic applications?
Lessons learned from networking at LinkedIn - “Kill the damn core”. They’re now running a single SKU CLOS network.
Sounds like lots of technologies died violent deaths in the LinkedIn data center. Casualties: - Core Switches - SNMP (yes, please!) - Syslog - SFlow The final three were all replaced with Kafka.

Comments

Popular posts from this blog