joneholland

14 ms·

91.
by joneholland 9y ago
We do heavy pipelining and tend to max out the single thread, so we run multiple redis instances per host.
92.
by joneholland 9y ago
You could link against native libraries. There were a handful of graphics libraries written in assembly that we used to do fast blitting and resolutions higher than 320x200. Back in those days, drawing a pixel was just writing to the vga me
93.
by joneholland 9y ago
Two of the largest customers of adwords are Expedia and Priceline. Why? Because almost every travel customer starts by typing their destination into google, and whoever has the top ad gets the booking. It's a fierce bidding war on keyw
94.
by joneholland 9y ago
Hi HN, I work for Expedia, so happy to answer any questions on how things work or dispel any myths. Ask away.
95.
How Expedia finds Flights(techblog.expedia.com)
3 points by joneholland 9y ago|1 comments
96.
by joneholland 9y ago
I'd assume the correct thing to do is a vector clock, where each blocks time stamp is nothing more than a offset from the previous blocks. It's easy to get most machines in agreement with how long a second is, but it's very v
97.
by joneholland 9y ago
Maybe because it's basically an ad?
98.
by joneholland 9y ago
That's because Expedia Inc owns all the others.
99.
by joneholland 9y ago
This smells strongly like farmed out to 3rd party creative agency work. Different domain, basic off the shelf PHP help desk software etc. A lot of time organizations don't have developers, and rather than work with the product organiza
100.
by joneholland 9y ago
We use the java stubs. We briefly looked at some scala proto generators, but most times you dump the proto class into a rich scala type right away anyways.
101.
by joneholland 9y ago
You can add Expedia to the list of production grpc users. Our entire hotel pricing backend is grpc microservices written in Scala. Some of these services take > 100k TPS. We have found grpc to be extremely scaleable. If that sounds inter
102.
by joneholland 9y ago
We've been happy teamcity users for years.
103.
by joneholland 9y ago
Thanks for letting us have access to all your personal data!
104.
by joneholland 9y ago
At least, when we didn't screw up :) Those were fun days.
105.
by joneholland 9y ago
So you built Basecamp?
106.
by joneholland 9y ago
And then two machines have the same seed and bam collision.
107.
by joneholland 10y ago
Expedia uses scala massively on the backend.
108.
by joneholland 10y ago
Why do people keep saying "the vendor"? It's hashicorp.
109.
by joneholland 10y ago
The app sucks, but apparently the critique is from someone who has never flown before.
110.
by joneholland 10y ago
That's valid, if the distribution of work is not fair, this won't work. In practice, when you are receiving enough traffic to make throttling practical you aren't usually throttling at 2 RPM across 2 servers.
111.
by joneholland 10y ago
The client doesn't do it. You put your front ends behind a load balancer like an ELB, or use a reverse proxy like Nginx. Edit: And yes, round robin is the most commonly used load distribution technique, and works very well assuming eac
112.
by joneholland 10y ago
No, you evenly round robin all traffic to all servers. Each server contains a map of tokens per per client filling at a fixed interval. That interval is calculated by taking the total global token refresh rate and dividing it by the number
113.
by joneholland 10y ago
You know you can implement a token bucket that doesn't share state between your API servers, in about 10 lines of code, using just a in memory map. Your incoming requests should be balanced across all of the servers so you just derive
114.
by joneholland 10y ago
These are terrible. Not because they don't test knowledge of scala, but because language trivia is a terrible way to identify a quality candidate.
115.
by joneholland 10y ago
Devops is not a role or team. It is a culture. You can't outsource that.
116.
by joneholland 10y ago
Sounds like they still use Brazil. I've never understood the mono repo argument. With something like Brazil (or even sonatype nexus), you end up in a much stronger place for guaranteeing consistency and immutability in your builds.
117.
by joneholland 10y ago
This is all good, if you are on git. Like I said in my other downvoted post... too many TBD zealots look at big companies that use it sans branches, and assume that it is the one true way, instead of understanding the larger picture (branch
118.
by joneholland 10y ago
I agree, which is also why I think monorepos are an anti pattern.
119.
by joneholland 10y ago
We don't put hard limits on our branch lifetime, but we groom stories with a goal to make them small enough so that the feature branch is very short lived.
120.
by joneholland 10y ago
I'm not talking about git flow.

More ›