HN user

gbrayut

579 karma

Current: Google Cloud Customer Engineer, Formerly: SRE at Reddit, Edge Platform at WalmartLabs, SRE at Stack Overflow

Mastodon https://hachyderm.io/@GBrayUT Threads https://www.threads.net/@GBrayUT

[ my public key: https://keybase.io/gbrayut; my proof: https://keybase.io/gbrayut/sigs/gjXWe_M0-pf2NttqXdOE_0cjYyuN9inOSy9Ev1DRLIc ]

Posts10
Comments80
View on HN

I connected an ESP8266 via serial protocol to the extra programming pins on a QMK based keypad (https://www.crowdsupply.com/anavi-technology/anavi-macro-pad...) so that it can have layers that directly trigger actions via Home Assistant API.

Also use the Bee Motion ESP32-S3 (https://www.crowdsupply.com/smart-bee-designs/bee-motion-s3) for their PIR motion sensing and running other sensors around the house.

And I have an old Wemos D1 mini connected to my Arduino based smart garage door that helps automate things like lock/unlocking the front door or triggering other presence based actions.

Curious on your thoughts about the "Sovereign Cloud" features discussed at https://cloud.google.com/blog/products/identity-security/new...

Would having a 3rd party host the services in the EU meet your requirements? Or having data residency restrictions with strict key management, EU based support, and access transparency/approvals?

IMO Google is also taking this seriously, but I am genuinely curious if any off the above would meet your requirements.

Many TLDs don't count (letter dash letter) as a premium/reserved domain like they do for other dictionary words or 2-3 character domains. Looks like v-s.space is claimed but for example z-s was just $9.99 a year

I used that trick when .dev was launched and snagged a-z.dev for all my future domain name needs

Strata was the custodian for LendingClub IRA accounts, but sounds like they have had some sort of falling out recently. Got an email this month about switching to https://www.altoira.com/ and then another from Strata trying to get me to stay. Now Stratas charging $100 fee for any accounts that didn't renew earlier this year.

I've only ever used their site when moving money in or out of the IRA but it's a pretty terrible UI and they don't seem to be very responsive. I've had a withdraw pending for over 4 weeks now trying to move money to another custodian.

You are probably better off finding a different approach.

Reminds me of a Windows installer I working on many years ago, that seemed to take a long time using CPU but otherwise not doing any real work. Turned out the SDK we were using tried to update the progress bar every kilobyte or something like that, and our near-gigabyte sized packages filled the message loop with a bunch of pointless updates (30.001% -> 30.002% but both displayed as 30%).

Once the vendor fixed the issue it shaved a few minutes off the install time that had previously just been a UI glitch (processing the large backlog of progress bar update messages).

Case in point, one of my favorite system architecture/design blog posts:

Providence: Failure Is Always An Option

https://jasonpunyon.com/blog/2015/02/12/providence-failure-i...

Which has one of my favorite quotes about scope creep:

Kevin and I have essentially become allergic to big projects. We attempt to practice “What can get done by Friday?” driven development. Keeping things small precludes a whole class of errors like “We need a new datastore”, ‘cause that ain’t gettin’ done by Friday. It’s hard to sink a week on something you weren’t supposed to be working on when all you have is a week.

Is there any way to setup a sharding solution for Prometheus? Like instances per AZ or that only scrape a certain set of nodes? On our larger clusters we had issues even with the optimized Prometheus instance in kubecost, and it's starting to look like metrics collection/processing may be a big driving force on our cluster scaling designs.

My last job used https://github.com/opserver/Opserver which had a pagerduty tab. Nice being able to see who was the on call and have instructions for when/how to page out.

It also has a "take on call for the next hour" button, which (for logged in users that matched a pagerduty user) would create an override for the next hour. Really handy when you are starting a change window and don't want to risk waking up the on call.

Neat! We use a similar Go based proxy for our tier 1 ingress and routing at Walmart Labs (global eCommerce), with Lua/Go plugins for edge/serverless style backends. It is a custom/proprietary codebase but the tech stack has served us very well. Great to see open source projects with similar use cases. I may have to play with this for use in some personal/hobby projects.

I look forward to hearing more about your plans for ingress and how the various pieces fit together (CDN, L4/L7 LBs, TLS termination, Geo/policy DNS balancing). Especially regarding the performance and new features available using Envoy. I've use HAProxy before and it was great for simple routing/reverse proxy but not so great at complex/dynamic configuration or cert management.

Awesome blog post! I very much enjoy hearing how large web properties implement these technologies and any issues they experience along the way.

Are you using envoy at all in your main http ingress path? You mentioned haproxy and AWS ELBs, but it wasn't clear if envoy is also being considered for public ingress traffic.

Keep up the great work!