HNHacker News
TopNewBestAskShowJobs

vp8989

754 karma · joined January 4, 2019

submissionscomments
vp8989··on Postgres scaling advice
The thinking on efficiency vs scalability is largely influenced by the US tech company meta where founders give up equity so they don't have to worry about profitability for a very long time.

In that case, it is preferred to burn piles of cash on AWS instead of potentially needing to sacrifice revenue because you can't scale quickly enough.

An architecture that is not scalable is considered a failure whereas one that is complex and inefficient is much more tolerated (as long as it can scale out) ... at least until the funding dries up or Wall Street activists get involved.

vp8989··on Fulfilling the Promise of CI/CD
The article talks about Continuous Deployment.

IMO Continuous Delivery is kind of a nothingburger vague process term that lots of people can (and do) talk themselves into saying/thinking they are doing. That's kind of the theme of this blog post BTW. Continuous Deployment is the actual indisputable thing (you either automatically deploy new commits in mainline or you don't) that gives you the real benefits but which lots of orgs aren't yet doing.

vp8989··on Fulfilling the Promise of CI/CD
Anecdotally this has largely been my experience, too.

TL;DR ... everyone has Jenkins but they can't just let it deploy stuff because there is tons of "professionalism theatre" bureaucracy baked into the SDLC implemented as crappy homegrown scripts that check you filled in fields in JIRA. On top of that the org likely has incorrect thinking that the way to reduce bad outcomes from software is to change it less often.

vp8989··on Fulfilling the Promise of CI/CD
That's not CD though.
vp8989··on Haskell is our first choice for building production software systems
Optimizing for worker fungibility, in a vacuum, seems like a -EV "playing not to lose" strategy. It's understandable that this line of thinking is common though.

I also believe that to be the case as an employee. Ie, being a generalist is probably -EV for your career but it feels safer so it's kind of a contrarian position to say "be a specialist".

vp8989··on Haskell is our first choice for building production software systems
No it isn't, it's a simple matter of fact statement that running code on runtime A appeared to be cheaper in terms of hardware costs than runtime B.

The "overlooking" part you filled in yourself in bad faith and bad reading comprehension, as the author actually does acknowledge that the observed hardware savings are small compared to the cost of hiring programmers.

vp8989··on When Amazon Switched from Sun to Linux
That's funny because AWS definitely feels like the IBM or Sun of this current era. I wonder what comes along next or if AWS is the "end of history".
vp8989··on My Experience at Apple
The secretive nature of their product development and the supposed "allure" of being an employee there seem like they would combine to enable particularly douchey forms of management.
vp8989··on My Experience at Apple
That is true. The parent probably meant to say Visa not Green Card. I can definitely relate to the feeling of being "stuck" in a bad situation while on a Visa and/or while waiting for a green card to be processed. It's such a huge relief when you finally get that freedom to move around in the job market.
vp8989··on The Big Little Guide to Message Queues
It's better to use a SQS standard queue and have the consuming system provide the exactly-once processing guarantee for various reasons. You will need to introduce something like Redis, if you are not already using it, but I still think it's net superior to using an SQS FIFO queue if you want exactly-once processing.
vp8989··on Hate Your Job
In my ~10 year career so far, I have found that this idealism can actually make things worse.

It seems that jobs in general can at best only offer short windows of time where the stars line up for you such that you can honestly say you enjoy working that job. But for one reason or another the window always closes. (Reorgs, you master the work so it gets boring, people come and go etc ...)

If the baseline level of pay in a field is high enough, it seems net detrimental to be highly engaged.

Who is better off? A checked out Engineer who collects 90-100k and is able to cruise at 6/10 levels of happiness under most conditions or a "striver" Senior Engineer who gets 130k but is pretty much always unhappy at work for one reason or another?

vp8989··on Hotwire: HTML over the Wire
The greatest trick the devil ever pulled is convincing people that shared hosting is preferable to dedicated, and then charging them way more money for it.
vp8989··on The Gervais Principle, or the Office According to “The Office” (2009)
That isn't an actual quote from the article. The article series quite clearly explains that these people are economic losers because they trade their time (just like the clueless and some sociopaths) for a paycheck but have neither the higher floor of the clueless or the higher ceiling of the sociopaths.
vp8989··on AWS CloudShell
It seems inevitable that remote dev environments will become ubiquitous.

With increased distribution of systems, increased use of cloud proprietary infra software that you can't run locally and now these custom SOCs. Companies are just going to give up on local dev environments and force everyone to write code in a browser.

vp8989··on Optimizing Lambda Cost with Multi-Threading
"I assure you that somebody does need to manage it"

You can always tell who has had to live with non-trivial serverless systems in Prod and who is just parroting the marketing copy.

vp8989··on Burnt $72k testing Firebase and Cloud Run and almost went bankrupt
But then I don't get to be a "serverless hero" and write blog posts about how my side project (that no one uses) costs $0.000034 to run instead of $5.
vp8989··on Burnt $72k testing Firebase and Cloud Run and almost went bankrupt
"The downside of disabling active resources is huge. It would mean a catastrophic interruption to the customers application exactly when its the most popular/active."

Lol what ... this is exactly what happens any time you hit a rate limit on any AWS service. The customers application is "catastrophically interrupted" during its most popular/active period.

The only difference is in that case, it suits AWS to do that whereas in the case of respecting a billing limit, it doesn't.

vp8989··on A former Uber engineer's disaster story
There is no cohesion or elegance at those kinds of head counts. There are just too many cooks, too many different perspectives, most toolchains allow you to solve problems in too many different ways.

IMO and contrary to what people say, making good software is not a team sport.

You could try to offset that by some combination of keeping head count low, optimizing for technical homogeneity when hiring and/or using intentionally spartan toolchains (Golang for example) but the odds are still against you.

Also, US business culture is maximalist and land-grabby in nature so no one is going to let you actually apply any of those constraints. The people who write checks don't actually care if the software is "good" because in almost all cases it doesn't have to be.

vp8989··on How we processed €5M in donations in 2 hours using Cloudflare and Stripe
"Why is running a bursty load on serverless negligent?"

Because Lambda and any other FaaS platform are always going to have some limitations as to how fast they can scale out. When you put stuff on TV, this is as bursty load as it gets. You are literally telling everyone viewing that TV channel at that time to pick up their phone and browse to some link.

If you are expected to handle all this load, the only way to ensure you can handle it is to over provision. The FaaS may promise some burst rate, but ultimately it's a shared hosting platform and if they have to choose between giving you your 3000 containers or keeping the other X customers running on those same boxes healthy they will always opt for the latter.

Worst case for them, they refund you the few bucks you paid for Lambda during that time. Worst case for you is you miss a ton of payments/donations/whatever. Welcome to the cloud.

The Stripe API has rate limits of 100/sec: https://stripe.com/docs/rate-limits

They put that to protect themselves from getting overloaded and Im sure these limits are more than plenty for typical use of Stripe which would be well spread out throughout the day. But when you put something on TV, 100 RPS is no way near going to be enough.

vp8989··on How we processed €5M in donations in 2 hours using Cloudflare and Stripe
I believe what is being implied is that because Cloudflare Workers operate inside of a much lighter construct, they are able to burst to higher concurrency inside of shorter time windows. Lambda can burst to 3000 and then an additional 500 more per minute after that.

https://docs.aws.amazon.com/lambda/latest/dg/invocation-scal...

Based on the scale mentioned in the article (hundreds of RPS) it's likely Lambda would also have been able to handle it just fine.

On another note, using non-provisioned infrastructure (aka "serverless") for an expected bursty load (TV campaign) is bordering on negligence. It sounds like lots of potential donations were missed because the Stripe account was not set up to cope with the load. It turned out to be a wash because Stripe donated 100k but if you change the business context of this system from "receiving donations" to "taking credit card payments" ... this outcome would not be considered acceptable.

vp8989··on Scaling Datastores at Slack with Vitess
It's not the same, you can't scale out from 1 writer on Aurora.
vp8989··on Scaling Datastores at Slack with Vitess
It looks like Azure has now integrated Citus into it's Postgres offering, but Im curious why AWS hasn't integrated either Vitess or Citus at all?

It seems like a well executed combination of Vitess/Citus + read replicas pointing to decoupled page storage would result in a fully featured non-proprietary database that scales all the way down to your laptop and all the way up to the heaviest OLTP use cases. If that existed, only truly masochistic people would continue using things like DynamoDB.

vp8989··on Dropbox saved $75M over two years by building its own infrastructure (2018)
"Very few web apps will ever serve as much traffic as SO."

Their traffic is like 80-90% reads and they actually hire good devs and let them work on perf.

Neither of those things are true in typical companies.

vp8989··on Dropbox saved $75M over two years by building its own infrastructure (2018)
"Instant elasticity in cloud is a myth"

This times a million. I think SQS standard queues are probably the only thing that IME actually fulfill that promise.

vp8989··on Conservatives flock to Parler, claiming censorship on Facebook and Twitter
Well presumably the parent to my comment is implying that echo chambers are only problematic if they are "imposed" upon you by "the algorithm", which I would disagree with.

The problem is that people have become hyper-partisan en masse and whether they arrived there because of "the algorithm" or because they intentionally filter out sources they disagree with ... it doesn't really matter.

https://www.allsides.com/filter-bubbles

The real problem (in my humble opinion) is that there is too much news and it's almost all intentionally biased to some extent. It's therefore not practical for people to keep up with the news without entering an echo chamber. You would have to, for each instance of "news", read at least 3 versions of it to ensure you are considering all perspectives. No one is going to do that.

Do people want to consume net unbiased news? Everyone says they do but consumption patterns says otherwise. Is it commercially viable to produce unbiased news? It used to be favorable but now distribution is cheap and there is more competition so the incentives are to be more biased and find a niche.

I don't think this is a solvable problem, the genie is out of the bottle. This is just a price we pay societally for having the Internet.

vp8989··on Moving my serverless project to Ruby on Rails
"AWS's Serverless Application Model explicitly supports local testing."

It doesn't provide any additional capability that was already there. Ie, I could already run my arbitrary function from the CLI by building a simple wrapper that reads a JSON file and sends it in. Or wrap it in a simple HTTP server.

The debugging story using that tool is worse than how I would already do it pre-SAM and they don't even have documentation for every runtime they officially support:

https://docs.aws.amazon.com/serverless-application-model/lat...

It doesn't allow you to test any of the interesting bits, which is what the blog post was alluding to.

- What happens if I have an SQS Lambda with 100 concurrency and a few of the containers get into a bad state? Do the other ones keep going or does the whole thing grind to a halt?

- What happens if I have a Lambda that consumes from 50 Kinesis shards and some of the containers get into a bad state?

- What happens if my Lambda throws an exception, what happens to my SQS message or Kinesis record?

If you outsource the plumbing you can't actually test the system locally you can only test "units" of it and in a lot of cases you either have to do remote tests with print debugging to figure out what's going on or what is more common is blindly assume the plumbing works how you intend, ship it to Prod and then fix problems as they occur.

vp8989··on Conservatives flock to Parler, claiming censorship on Facebook and Twitter
"No, I think there's a big difference between an echo chamber constructed by algorithms that push content upon you without your consent or knowledge, and an "echo chamber" constructed by yourself when you actively curate and trim the media you consume."

What is the difference?

vp8989··on We need less powerful languages (2015)
It's certainly possible for individuals to swim against the current. I am not a Go programmer but all the Go open source code I have read has been brutally simple and easy to consume. I don't think that's a coincidence.
vp8989··on .NET 5.0
.NET/C# are great platforms, it's the median .NET/C# developer and the general culture of working at one of these shops that ruins it.

Just decades of over-engineering OOP "best practices" baggage that is impossible to shake off.

Why do people "move" to new languages? Mostly to leave the baggage behind.

vp8989··on .NET 5.0
In their defence, there is a default builder that would save you maybe 3-4 lines there, but I do generally agree with your point.

It is something that annoys me about .NET in general there is just decades of over-engineering cruft and once these practices emerge its difficult to get people to stop doing them. The problem only gets worse as time passes.

← PreviousPage 5 of 7Next →