Matthias Endler

That's always a good thing that managers want to hear because saving costs becomes much easier if you can just shut down some of those nodes if you don't need them at the moment.

Impressive.

How many queries per second does one box do?

And how much CPU does it use, roughly?

Would you say it's a rather CPU or compute bound problem or a storage or IO bound problem?

Because on one side you have hashing, which can be very expensive, but maybe that's just a thing that you do at the beginning when you boot up and then it's not really as compute intense later on during operations.

Or would you say, well, no, actually that is kind of the bottleneck?

Or would you say, no, the storage part is the bottleneck?

Yeah.

You said it yourself, lots of moving parts.

What's the median latency of a forward geocoding request?

And maybe a reverse geocoding request in comparison.

Nice.

And all of that with how many lines of Rust code in total for the server implementation at the moment?

Are there any tips and tricks that you could share with people who are planning to build a larger Rust application?

I'm thinking of composition patterns, usage of traits, how you structure your data, data objects, immutability, anything that comes to mind that you learned maybe that is uncommon in Ruby or Scala or any other language that you knew before?

It's the root of all evil.

Yeah, perfect.

That's right down my alley, even in a geocoding sense, because I recently wrote an article called Be Simple, and I'm very much in favor of that.

Unfortunately, we're getting close to the end.