News for hackers. Stuff that matters.
Re:Building Facebook's Service Encryption Infastructure by dirkg on Wednesday May 29, 2019 @12:43PM (#20042374)
I wonder what the performance differences are with their approach vs using K8s + service mesh of your choice which includes all this.

I imagine Google runs a bigger scale operation on top of Borg and their internal service mesh.

Re:Building Facebook's Service Encryption Infastructure by Diederich on Wednesday May 29, 2019 @12:46PM (#20042420)
Borg != Kubernetes k8s is based on Borg, but they are quite different.

Companies at this scale have integrations between all different levels and layers of the 'stack' that make the use of off the shelf software difficult or impossible.

Re:Building Facebook's Service Encryption Infastructure by dirkg on Wednesday May 29, 2019 @01:39PM (#20043075)
yes I know they are different, but the lessons learnt/dev in both products probably end up influencing each other.

My point was encryption of services is built into K8s/service mesh and wondering how it fares compared to FB's approach.

Re:Building Facebook's Service Encryption Infastructure by sudoyear123 on Wednesday May 29, 2019 @02:49PM (#20043894)
This would make a great comparison. I'm not certain whether or not K8's mutual auth supports session ticket resumptions and distribution of short lived ticket keys. The ticket rotation design would probably make a great addition to K8. There are a lot of intricate details in design which can make a major difference in not only performance but also whether or not the system wakes you up at night.
Re:Building Facebook's Service Encryption Infastructure by brown9-2 on Wednesday May 29, 2019 @07:48PM (#20046920)
Kubernetes does not have a built-in mutual auth solution