These components are very different in complexity and scope. Let's be real: a seasoned developer is mostly familiar with load balancers and ingress controllers, so this will be mostly about naming and context.
I agree though once you learn about k8s it becomes less mysterious but that also means the author hasn't pushed it to the limits.
Outages in the control plane could be pretty nasty and it is easy to have them by creating an illusion everything is kind of free in k8s.
No load balancer means... entering one node only? Doing DNS RR over all the nodes?
If you don't have a load balancer in front, why are you even using Kubernetes? Deploy a single VM and call it a day!
I mean, in my homelab I do have Kubernetes and no LB in front, but it's a homelab for fun and learn K8s internals. But in a professional environment...
I don't think it would be possible for them to stay with AWS considering their storage volume usage. As soon as the storage was out everything else has followed as well
Dropbox's business IS storage, which means running on top of storage is always going to be a threat and cut into their margins. What incentive does AWS have to give Dropbox a really sweet S3 deal? They know Dropbox needs the storage. It's like why it's better for a business to own the building its in, because if you become successful, your landlord has the incentive to increase your rent. This isn't about if AWS can provide a compelling bulk rate for S3, it's about if your business lives or dies based on the AWS deal renegotiation.
No, I don't think that Dropbox should manufacture its own hard drives. The main reason is that switching hard drive manufacturers can be done piecemeal as you need to buy them. Getting data out of S3 if the contract negotiations go bad can cost more than storing it. It's just very different economics and level of vulnerability given the two.
Sure, that was a great feature in 2007. (S3 existed when Dropbox was founded, FWIW.)
It eventually stopped being a differentiating source of value, and trying to out-commodity the CSP’s on storage cost at scale seems like a bad strategy to bring value back to the product. At tremendous effort you make it possible to lower prices by 20% or whatever, in order to keep the same profit on an undifferentiated product. Who cares?
Go team has built a remarkable tool under your leadership. A tool that moved a niddle to the better side of things for the industry. Thank you and God speed!
From the blog post, the largest individual Ray cluster that was observed running a production compaction job in Q1 had 26,846 vCPUs and ~210TiB of RAM. This is roughly equivalent to a Ray cluster composed of 839 r5.8xlarge EC2 nodes (w/ 32 vCPUs and 256GiB RAM per node).
Been there yesterday, can confirm what the author wrote about immersion. Cathedral and opera scenes are something I have never experienced before, fully blown away. The storyline is garbage.
can't do image search in a photos app too which is a major bummer for me personally. I protocol things there and it's impossible to find without annotations.
(person who made that video and just found this post through youtube analytics here)
Yes, it is a lot more complicated this is because of the nature of what the gyro is doing. The gyros are effectively a 4 dimension rotation of the puzzle that actually doesn't change the state of the puzzle, but just the orientation. This doesn't work out to be very pretty in 3d.
I also listened to NPR with a couple of scientists who has worked on JWST and they said there were times when they felt pretty down on news JWST would get cancelled or NiRCam would need to get removed from the program.
