mleonard

Thanks Google cloud team this looks really great. Quick question: Is Cloud Run a zonal or regional resource and is there any way to put this behind the global load balancer? Thanks.

Thanks Google cloud team this looks really great. Excited to hear more on the Next livestream. Questions: Is Cloud Run a zonal or regional resource and is there any way to put this behind the global load balancer? Is Http2 (grpc) support planned? Thanks.

Typo: It should be 'built-in' not 'build-in'

Anyone know if this will run on a Pixelbook? (inside the Crostini linux virtual machine in ChromeOS). Thanks

Hi James and Angel congrats on the launch! Great issue to try to solve, hope you succeed.

Thanks for the LAUNCHHN voucher code. I'd seen cspa.io on hackernews previously but the free voucher code was the motivation I needed to register for the core exam in April! I'm a uk-based maths grad previously in a datasci role, currently taking some time off to self-study computer sci and frontend/backend. Looking forward to checking my progress against the test!

Quick bits of feedback in case they're helpful:

(1) I'd love there to be a second practise/past paper available (there's only one currently right?). Ideally I'd like to go through one now to check where my knowledge gaps are... then take one a couple of weeks before the exam in April.

(2) I just gave this only a very quick read... and found it a bit unclear: https://cspa.io/scoring. I'm sure I could understand it no problem with a more serious read-through... but thought I'd feed that back anyway. [Specifically it's not clear in the examples section how the score of 440 in FE is achieved, as the max mentioned is 400. Also the 6 subject scores all differ... but then presumably are scaled to 400 points. Is that right? With my quick read through I'm not yet clear if in the exam I should try to complete all 6 or just complete 1 of the 6 subject areas. I guess as final score takes your best score out of the 6 you could just complete one or two. What do most candidates do in practice? Perhaps you could add some guidance on this to the site somewhere if it's not there already.]

Regards. Mike.

Thanks! Yep didn't post it on kobule. :)

Congrats on the launch. How does it work on your end? Are you using an official API or doing it another way?

This is really great good job! First thing I thought when I saw Carlo was I wish there was a go version! I'd love to see this under the GoogleChromeLabs github organisation alongside Carlo so that it gets the same exposure and community involvement. Would you consider reaching out to them?

Source available somewhere? Would love to take a look. If not... could you explain the bit fields approach a bit more please? Thanks

A few questions come to mind after reading the docs (minus the currently 404ing ones): (1) is this a zonal or regional product? ie does it replicate data across zones in a region? (2) roughly what latencies should I expect to see? eg for the following: a 1KG, 1MB, 1GB read and write. Any info here would be helpful. (3) does it have close-to-open consistency? or something weaker / stronger? (4) any plans to add gcp pub/sub integration somehow? would be great to be able to subscribe to changes like with other gcp storage products. (5) any plans to move from NFSv3 to NFSv4? (6) backups available or planned as a feature? eg to GCS (7) can you share anything about how it is implemented?

Thanks

Says it supports CloudSQL? Does it support Cloud Datastore / Firestore or are they on the road map does anyone know?

Would someone from Facebook be able to comment on LogDevice versus (Twitter's) Apache Bookkeeper/DistributedLog??

The two sound very similar. I've been studying Bookkeeper this week to understand how it works and was excited to see the blogpost about LogDevice.

My understanding isn't fully there yet, but BookKeeper seems to have a more involved protocol versus LogDevice: ie it has fencing to ensure that only one writer is writing to a log at a time a 2-phase-commit-like protocol, and opening/closing of ledgers.

To me LogDevice's sequencer and epoch number sounds much simpler. Does BookKeeper achieve some more consistency or other guarantees that LogDevice doesn't by having a more involved protocol? How do the two compare in terms of goals/pros/cons/tradeoffs/usecases/etc?

(From reading the blog post it seems to me that in LogDevice an old sequencer could still be writing to LogDevice when a new one with a higher epoch number is also writing. As I understand it BookKeeper uses a CAS operation on metadata version number (like the epoch number of LogDevice) AND fencing on the storage nodes to make sure that only a single writer is writing at a time).

>> We ensure that only one copy of every record is read from disk and delivered over the network by including the copy set in the header of every record copy. A simple server-side filtering scheme based on copy sets coupled with a dense copy set index guarantees that in steady state only one node in the copy set would read and delivery a copy of the record to a particular reader.

Can someone explain/expand on the above please? I've read the article a couple of times and tried to understand the above paragraph in context but I don't get it.

Will the content for the courses be released all at once? I'd like to complete the 5 courses in approx 1 month.

Do you have an examples of how to get started with Telepresence and a go app? Thanks

Great blog post, looking forward to the upcoming blog posts you mentioned at the end.

Could you explain "sending messages to other keys in the same group via a loopback topic, e.g., useful in machine learning applications" briefly if you wouldn't mind? I understood the rest of the article but this sounds interesting and I'm not quite sure what you mean! Thanks

Also: I'm curious what you think of zetcd that coreos recently blogged about, given that you use kafka in production and use go? Something that's put me off kafka in the past is managing zookeeper, and also less support in go. I'm excited that soon I might be able to use kubernetes + etcd + etcd operator + zetcd + kafka + goka.

I'm currently evaluating using create-react-app. Could someone please confirm the following for me: (1) Without ejecting, it's not possible to use 'styled-components' (2) Would need to eject to do server-side rendering (3) There's no hot module reloading

Not saying these things are deal breakers at all, create-react-app is really great. Just making sure I've got my pros and cons list correct! Thanks for any help

Great write-up and thoughtful responses here on HN.

Very interesting that you've used Cordova. For a simple chat-based app that approach makes a lot of sense as you can push updates any time. Would you be able to share any chat-ui cordova libraries you've used or anything helpful in that regard? Or was it all custom built? Would you choose cordova if you were building the same app now or is there something else you'd consider using?

Also: your ruby DSL sounds interesting. Do you push the entire json syntax tree to the client? Chatbot platforms typically work by sending a user's chat message to a server then responding... so I'm interested how you've found doing things locally with a json syntax tree (assuming that's what you meant) and what were the pros/cons/trade-offs of that approach?