text
stringlengths
0
1.49k
[1145.14 --> 1145.62] GKE.
[1145.62 --> 1147.40] GKE, yeah.
[1149.04 --> 1150.08] So, yeah, I mean,
[1150.18 --> 1152.92] that's kind of like the perfect world, right?
[1153.14 --> 1154.98] You get all the benefits of Kubernetes.
[1155.24 --> 1156.56] You only have to focus on
[1156.56 --> 1160.16] developing apps that are kind of cloud native and run on it,
[1160.20 --> 1161.92] and you don't have to worry about the infrastructure.
[1163.92 --> 1164.78] Yeah, well,
[1165.92 --> 1166.64] at VMware,
[1166.64 --> 1170.40] it's a fairly interesting mix here
[1170.40 --> 1171.84] because by definition,
[1172.14 --> 1174.22] people are worrying about the infrastructure
[1174.22 --> 1177.32] because we have this vSphere product.
[1178.30 --> 1180.52] So the people we go to
[1180.52 --> 1183.44] typically know how to deal with hardware
[1183.44 --> 1186.62] and all of the failure scenarios that come from there.
[1187.72 --> 1188.86] I do think that
[1188.86 --> 1191.54] it's this interesting thing.
[1191.68 --> 1193.62] So Kubernetes allows you to package your app
[1193.62 --> 1196.02] and deploy the containers
[1196.02 --> 1197.70] and do all of that service discovery,
[1197.82 --> 1198.90] all of the cloud native stuff
[1198.90 --> 1202.38] you actually require to run these larger infrastructures,
[1202.38 --> 1205.12] but I think most people are surprised
[1205.12 --> 1206.92] by how much Linux you have to know
[1206.92 --> 1208.82] to really operate it well
[1208.82 --> 1211.40] because it doesn't hide anything from you.
[1211.56 --> 1212.62] It's there.
[1212.76 --> 1215.42] It makes extremely creative use of the kernel facilities.
[1216.50 --> 1217.38] And so it's a very...
[1218.44 --> 1220.22] Technically, it's a very interesting project.
[1220.22 --> 1222.60] Yeah, it's a lot of fun.
[1223.44 --> 1226.58] And I think that there should be experts in that stuff too.
[1226.72 --> 1227.46] Don't get me wrong,
[1227.58 --> 1229.32] but a lot of businesses,
[1229.56 --> 1231.06] especially smaller businesses,
[1231.40 --> 1232.98] they're worried about
[1232.98 --> 1237.20] having to scale fast and things like that.
[1237.20 --> 1238.50] And then, you know,
[1238.56 --> 1241.52] once you start hitting odd scenarios
[1241.52 --> 1242.46] and stuff like that
[1242.46 --> 1244.00] and you hit saturation points
[1244.00 --> 1246.26] and things fail in odd ways,
[1246.34 --> 1249.08] and then your team who was developing features
[1249.08 --> 1251.16] now becomes firefighters
[1251.16 --> 1254.22] trying to figure out some of the issues
[1254.22 --> 1255.18] and things like that.
[1255.88 --> 1256.84] So, yeah.
[1256.94 --> 1258.94] And I mean, it's a fun world, right?
[1259.00 --> 1260.70] Like some of us enjoy doing that,
[1260.76 --> 1262.90] but not everybody has the extra resources
[1262.90 --> 1264.30] to be able to do that.
[1264.30 --> 1265.30] And like you said,
[1265.46 --> 1267.96] with the on-prem people and stuff like that
[1267.96 --> 1269.36] that are used to running vSphere
[1269.36 --> 1270.52] and things like that,
[1270.66 --> 1275.32] they've already got that expertise on their team.
[1276.08 --> 1278.74] And not every team is fortunate enough
[1278.74 --> 1281.52] to have the kind of infrastructure expertise.
[1282.60 --> 1282.80] Yeah.
[1283.22 --> 1284.68] I'm very interested to see
[1284.68 --> 1286.54] what's going to happen with Istio
[1286.54 --> 1290.04] because that's a very puzzling project to me.
[1290.26 --> 1293.18] Like I understand the problem it's trying to solve,
[1293.18 --> 1295.42] but I think most businesses
[1295.42 --> 1296.86] who are looking at these solutions
[1296.86 --> 1298.06] are latency sensitive
[1298.06 --> 1299.70] and I don't know how Istio
[1299.70 --> 1301.76] is going to solve that particular problem.
[1303.18 --> 1304.24] Because at the moment,
[1304.66 --> 1305.84] when we run our simulations,
[1306.98 --> 1308.58] it adds so many hops
[1308.58 --> 1310.98] that it becomes a weird proposition.
[1311.72 --> 1313.96] I really want to see the service meshes take out
[1313.96 --> 1315.34] because in the end,
[1315.42 --> 1316.76] the distributed system problems
[1316.76 --> 1317.92] are being solved there
[1317.92 --> 1320.16] with the circuit breakers
[1320.16 --> 1322.16] and all of these calling patterns
[1322.16 --> 1323.50] that they encapsulate.
[1324.18 --> 1326.84] But it's going to take some work still.
[1327.48 --> 1328.58] So that's the thing
[1328.58 --> 1330.10] I've been looking into lately.
[1331.16 --> 1331.28] Yeah.
[1331.30 --> 1332.68] There's a lot of interesting things
[1332.68 --> 1333.48] that have popped up
[1333.48 --> 1335.80] in maybe the last six to nine months.
[1335.80 --> 1336.92] You've got Istio,
[1337.22 --> 1338.20] Envoy,
[1339.04 --> 1340.36] that came out of Lyft.
[1340.80 --> 1341.96] Like that's super interesting.
[1342.72 --> 1344.28] And all of these are so early,
[1344.28 --> 1345.26] and they work
[1345.26 --> 1346.46] and they solve problems.
[1346.58 --> 1347.90] But I'm really interested to see
[1347.90 --> 1350.36] what the version twos
[1350.36 --> 1352.14] and threes of those look like.
[1352.56 --> 1353.14] Because like you said,
[1353.20 --> 1354.98] you kind of add additional hops