Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jbeda
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
jbeda
10y ago
It was me, Brendan and Craig McLuckie.
32.
▲
by
jbeda
10y ago
I prefer "Cloud City"
33.
▲
An Ode to Boring: Creating Open and Stable Container World
(medium.com)
5 points
by
jbeda
10y ago
|
0 comments
34.
▲
by
jbeda
10y ago
Avalon was the original codename for WPF. It is a great example of what you get when people vote on codenames.
35.
▲
Recipe: Docker Logs → Google Stackdriver Logging
(eightypercent.net)
1 points
by
jbeda
10y ago
|
0 comments
36.
▲
by
jbeda
11y ago
It isn't "gate checking" as your bag will show up in baggage claim with the other checked bags. They'll sometimes do real gate checking for people in first but it usually isn't necessary.
37.
▲
by
jbeda
11y ago
Gory details: https://github.com/kubernetes/kubernetes/issues/8132
38.
▲
by
jbeda
11y ago
I just want to give a public shout out to Wojtek on this blog post. It shows scalability in for an actual scenario at levels that most users won't need (10M req/s!). Beyond that, there is a clear methodology with lots of hard da
39.
▲
by
jbeda
11y ago
It gets a lot harder to name things world wide if you don't start with "Google". gmail in Germany was a lesson: http://techcrunch.com/2012/04/14/google-finally-gets-right-t...
40.
▲
by
jbeda
11y ago
Funny story -- Google Container Engine was the obvious name for that product but the TLA for it (GCE) conflicted with Google Compute Engine. We broke the tie by deciding the TLA for Container Engine would be GKE. The 'K' is a no
41.
▲
by
jbeda
11y ago
Check out https://algorithmia.com/ . Stuff like this plus a bunch more. Real business model so you can have more confidence in it.
42.
▲
Screencast of new Kubernetes Dashboard
(youtube.com)
1 points
by
jbeda
11y ago
|
0 comments
43.
▲
by
jbeda
11y ago
> Facebook and Google don't really do Work From Home and don't have a lot of remote locations for development depending on where they are. I don't know what they offer datacenter staff, but in many areas, that's all t
44.
▲
KubeCon keynote: The Operations Dividend
(slides.eightypercent.net)
3 points
by
jbeda
11y ago
|
0 comments
45.
▲
by
jbeda
11y ago
If you want to use a reasonably priced non-Docker-run registry that is available today, check out the Google Container Registry: https://cloud.google.com/container-registry/ It recently hit GA and is super fast. You c
46.
▲
by
jbeda
11y ago
When operating at scale, you will, once in a while, have corruption. Even if you use ECC RAM, once in a while you'll have a double bit flip. And it doesn't look like Backblaze uses ECC ( https://www.backblaze.com/
47.
▲
by
jbeda
11y ago
Using a hash or CRC here is totally necessary. Often times CRCs in TCP fail due to corruption outside the network stack. Having an end to end check will catch, say, memory bit flips and such after data comes off the wire. But there is no ca
48.
▲
by
jbeda
11y ago
Took a quick look at the API. For context, I was involved in the early days of Google Cloud Storage. It is surprising that they didn't make it compatible with the S3 API -- at least for common object/bucket create/delete. Th
49.
▲
by
jbeda
11y ago
Very good point. I wrote a blog post on this topic to try and characterize different types of lock-in. http://www.eightypercent.net/post/types-of-lock-in.html This was as also part of the strategy when we decided to op
50.
▲
by
jbeda
11y ago
[Author here] I'd love to see a decentralized image naming and distribution system. I'm pushing hard for this to happen as part of the OCI. See https://groups.google.com/a/opencontainers.org/forum
51.
▲
by
jbeda
11y ago
Author here. Lots of comments on the term "modern" and the fact that this is container based. While there are obviously other ways to skin this cat, for me, I want the following out of my production stack: * Self healing and self
52.
▲
by
jbeda
11y ago
I think that there are disadvantages to using a PaaS. It can bring all of these components together, but it also means that you don't benefit from best of breed systems at each layer. Also, up until now most PaaSes were vertically int
53.
▲
by
jbeda
11y ago
Many of the layers defined there are necessary for any well run production system (things like logging and monitoring). A lot of the extra components allow for dynamic placement and management of workloads. This allows for the system to be
54.
▲
by
jbeda
11y ago
Very true this is container based and is very much in the style of what I experienced over 10 years at Google. I put a disclaimer in the post to that. I was also considering using the term "cloud native" over "modern" b
55.
▲
Anatomy of a Modern Production Stack
(eightypercent.net)
57 points
by
jbeda
11y ago
|
24 comments
56.
▲
by
jbeda
11y ago
Looks like 8i is using fewer cameras with a narrower field. The processing doesn't look nearly as clean. The compression doesn't look as good as it didn't download realtime. The MSR video claims that they can deliver their
57.
▲
High-Quality Streamable Free-Viewpoint Video [MSR/SIGGRAPH]
(research.microsoft.com)
3 points
by
jbeda
11y ago
|
2 comments
58.
▲
Operational Lock-In vs. Development Lock-In
(eightypercent.net)
1 points
by
jbeda
11y ago
|
0 comments
59.
▲
Microsoft Cutbacks: The 1993 "Shrimp and Weenies" Memo
(allthingsd.com)
1 points
by
jbeda
11y ago
|
0 comments
60.
▲
by
jbeda
11y ago
I haven't seen vagga before. It looks very interesting. But, since it is still using an OS based package manager (Ubuntu, for example) it doesn't address all of the issues that I outlined. Specifically packages can't be cac
More ›