I work with Wael. Development is still ongoing. One implementation uses Golang, the other uses F# with a library that wraps libuv for faster network performance. Pony was used to write the stress-testing client for both implementations.

I mentioned this elsewhere in the thread, but since you'll see the reply here; look into Vert.X if you haven't already.

It already does most of what you want and has support for native epoll transport.

I'm not sure what led Vert.X to be discarded, maybe not a Java shop? But we've used it extremely successfully for high performance REST and I know of several high profile tech companies that swear by it.

There's nothing I know of that compares with Vert.X in performance, stability, and popular adoption

Thanks for the recommendation! However, there are a few reasons why Vert.X wasn't considered, the biggest ones being that we're not a Java shop and the service in this blog post isn't HTTP/REST.

While the bandwidth benchmarks are fun to see and write blog posts about, we also care a lot about keeping tail latency at or below 2ms than we do about getting more bandwidth at this point.

Ah yes. The GC latency could be a problem. Java may still be viable with the new ZGC garbage collector. And Vert.X uses Netty underneath which is mostly protocol agnostic.

Still, those issues and not being a Java shop makes Vert.X/Netty likely a bad fit.

Thanks for replying with a well thought out response!

Have you considered Nim? You can achieve some really high performance with it[1]. Since you've considered Rust, Go, C and even Pony, Nim should really be on your list.

1 - See httpbeast in the latest round of the Techempower benchmarks: https://www.techempower.com/benchmarks/#section=data-r17&hw=...

Does Nim's compiler still crash all the time?

Also why is evey immature native language considered, but the two speed demon languages without garbage collection - ISPC and C++ - are nowhere to be found?

Was pony considered for the implementation itself? Other than the immature ecosystem it seems like a perfect fit here. Awesome write up and sounds like a fun job.

I'm really glad I came here and found this comment. It squares so many circles for me. Thanks rkallos.

Thanks for helping me answer all my questions about Pony! :)

You're welcome.

Do you use libuv on go side as well?

You don't want to use C lib in Go for performance reason.

Nope. The Go implementation uses net.Conn from the standard library.

> "I didn't want to rewrite everything from scratch, and definitely, I didn't want to handle all edge cases for epoll. My choice was to use libuv. The architecture I opt for: use 16 cores out of 40 for networking, having 16 'uv_loop' each running on its own thread. Callbacks will be passed from F# to each 'uv_loop' instance. The event loop will call them after parsing the bid request in C11."

Looks like libuv directly in C11? (not F# as before edit).

> The solution was to Marshal calls from F# to libuv and achieve 5 Millions (at least) bid requests/s on 16 threads (this solution scales with cores/NICs).

The language is called F# (pronounced F-sharp), not F$.

F$???? Is that a typo?

Could be a play on "M$"? A typo is probably more likely since the keys are next to each other.