When we first started Petabridge in January 2015, I never imagined that we’d be at this for 2-3 years, let alone 10! But here we are. It’s been an amazing journey and our privilege to work with so many amazing customers and software developers on building some of the world’s most important software on top of Akka.NET.

I already published a small post on my personal website about the business side of running Petabridge over this span of time, but for our subscribers and Akka.NET users here at Petabridge, I thought it’d be more appropriate to share some of the engineering lessons we’ve learned over the course of 10 years from all of our experiences here.

Please enjoy “10 Most Important Engineering Lessons Learned from 10 Years of Petabridge”.

The Lessons

For those of you who are not inclined to watch the video, here are the lessons:

1. Don’t get cute
2. If you can’t measure it, you can’t control it
3. Locality is the biggest factor in distributed systems’ performance
4. Leveraging .NET threading has a bigger perf impact than goofy micro-benchmarks
5. Version tolerance is a skill
6. Beware of developers who aren’t curious about how things work
7. Microsoft makes mistakes too
8. Good code eventually adopts functional styles
9. Idempotent designs simplify everything
10. Decay begins with the details

Thank You

Thank you very much for your support as a customer, subscriber, user, or just a general fan of what we do. We wouldn’t be here if it weren’t for developers like you. Thank you very much, from the entire team here at Petabridge.

If you liked this post, you can share it with your followers or follow us on Twitter!