Teams building the world's most important software

The paid support has been super helpful when we've used it.

This was probably one of the best, if not the best, training I ever had and I’m really looking forward to building with Akka.NET further.

We are very pleased with the Akka.NET implementation we are using in one of our main products.

Of course, having the on-site training gave us a big boost and greatly reduced the time we needed for developing the current version of the product. So, all in all, our experience with Akka.NET is pretty pleasant.

Stream anything natively on Kubernetes with Arcane — built on Akka.NET.

Interaction with the person fixing or advising on the issue has been quick and easy. Turn around of problems have also been quick and effective.

An observation I had around high CPU in Akka.Streams.Kafka was subsequently fixed in a later release. It was a very useful fix.

Deep knowledge of the Akka.NET stack and on architecture.

Fast and helpful responses.

It's not often you come across a programming paradigm that completely changes the way you write software — for all the right reasons. Akka.NET was one of those paradigms that has transformed the way I design and build highly reliable, scalable, and intuitive server-side systems.

I've been designing and building software for over 25 years in the manufacturing, commercial aviation and e-commerce industries. The Actor model, via Akka.NET, has made it so much easier to build and deploy these types of complex systems.

I have to thank the Petabridge team for their amazing work on building the framework for the .NET ecosystem, and for building a vibrant community around it.

The people who sign my bonus check are going to be happy.

Performance in the product I described was so great with 7,000 (!) excel-style grids, our biggest client decided to bump it up to 840,000 (!!) grids, a 120x increase. Yesterday. That got a little bit hectic… We shipped on time, though!

Overall, I feel like I was given a great head start. I could have lost several weeks to get this much info if I started a distributed system in Akka by my own.

It is a little expensive for a Spaniard... but it's definitely worth the money, I am very happy with what I have learnt!

At Tranzact we use Akka.NET in a cluster made of almost 150 nodes on production, leveraging on the sharding module to keep the state of each of our users.

We replaced our custom trace implementation with Phobos (Jaeger+AI), and it helped us quickly discover race conditions in our software and improve our error handling.

In pre-production development, we applied Petabridge's expertise to review our design decisions and approach, which taught me more about the framework, saved us a few production issues, and most importantly really gave us the confidence to proceed.

Our request for new product functionality was given due consideration. Petabridge support has been responsive and thorough.

When combined with the training programs that Petabridge offers, it's been a no-brainer for our team and a great return on our investment to date.

And it's not my fault that you guys made a product so good that I rarely must reach out for help!

We are happy with quick response to our issues and the depth of involvement in its resolution.