Aaron Stannard
@Aaronontheweb
Followers
7K
Following
14K
Media
1K
Statuses
25K
Founder and CEO @Petabridge @getsdkbin OSS: @AkkaDotNet Open Source Software, Space, .NET, and Startups Catch me on YouTube: https://t.co/gUNvkaMWLk
Houston, TX
Joined May 2008
The reminders system I'm prototyping handles a lot of the other ugly bits around dealing with retrying payments, due date enforcement, renewals, etc
Built a durable reminders / "distributed scheduler" system for Akka .NET actors yesterday. Wanted to use it for handling recurring billing and the multitude of deadline-driven edge cases that appear there. Client side invocation looks like this
0
0
0
But I'm pleased with it - definitely need to do a post mortem to see how this compares to the awful CRUD system we've been using for years
1
0
0
Still not done iterating on this design yet - have a bunch of scenarios that aren't fully baked (what happens at each of these stages when a user cancels their subscription? that behavior will be totally different depending on current state)
1
0
0
(there's a set of other actors that run invoicing, payments, and invoice number generation who are doing work behind the scenes to drive the state machine forward, as it would be done in production)
1
0
0
Testing a fairly big business scenario like a first-time purchase isn't that hard either - none of the code below requires a real database, network calls, or the real Stripe client either.
1
0
0
FUTURES TRADERS: Get 40% off all evals, no activation fees, end-of-day drawdown in our live-market PRO+ accounts…and still daily PRO payouts!
0
20
115
Each of these states are self-triggering and re-entrant. When the actor recovers its state from Akka.Persistnce, it will do things like re-request its invoice using the previously assigned id
1
0
0
The magic tricks to making this all work really boil down to actor behavior-switching and Akka.Persistence to make that fully re-entrant across restarts, crashes, upgrades, etc: https://t.co/YO72gOxDhq
petabridge.com
Akka.NET Actors' Hidden Super Power: Behavior Switching
1
0
0
Took the old CRUD tables and turned them into read models / projections of the actor's state, which is the new source of truth. Gives us backwards compatibility while also supporting tons of previously unfulfilled business requirements and eliminating the largest error source.
1
0
0
NEAR Intents just doubled its daily volume ATH with $200M in the last 24 hours 🔥 Unstoppable liquidity is NEAR
39
60
472
This domain entity is most complex piece of business logic I've ever had to handle (subscriptions with configurable payment terms, renewal frequencies, benefits, grace periods etc) but re-modeling it from CRUD to a state-machine (actor) makes it 10000x easier to reason about
1
0
1
https://t.co/liXMpqBUn0 - I keep coming back to this as one of my favorite code samples to work on because Blazor Server + @AkkaDotNET make it really fun + easy to sync multiple clients
github.com
Multi-player MS Paint application. Built with Akka.NET, Blazor, and .NET Aspire. - petabridge/DrawTogether.NET
0
0
2
I actually like Blazor Server because it's 1000x less work than getting SignalR + JS bindings equipped and can actually be type-checked using a single build system. I just wouldn't build anything that needs to be Google-indexed with it.
the best .net devs i know ignore the useless parts of the platform like blazor and embrace the best parts like aspdotnet core
4
0
13
F# is and has been extraordinarily expressive, without requiring a ton of new language additions.
@Aaronontheweb What always baffles me about F# is, how few features the language has (excluding all the OOP stuff that is mostly c# interop). It's quite expressive, with a very limited amount of language constructs.
1
3
23
The battle of self-hosted LLM pros 👇
@__tinygrad__ @DanAdvantage @KinvertOG @AllInOnBlack @theo ok how about this we each put up the 10k in escrow and each do our nanochat ( https://t.co/znfDgTFTtL) speedruns. You train on the tinybox server with 8x5090, I'll rent and pay for a 4x6000 Pro WS and give u root and everything (we can stop after pretraining, or do the full, idc,
1
0
4
Reminder: our @AkkaDotNET streams training is open to the public for today. If you can't attend live, GoToWebinar will send you a recording afterwards. Runs from 11am to 1-1:30pm Chicago Time today.
Register here:
0
1
7
Based and Actor-pilled. My secret admission is if I were rebuilding MSBuild from scratch it'd be explicitly actor-based. It's basically a local-only actor system anyway, just lacking a lot of the nice operational controls.
I have the beginnings of a HangFire replacement here if I abstracted away the actor bits, which is doable. 1. Have a general purpose IScheduledTask interface that defines a job with some input parameters 2. Create a dashboard that tracks tasks / allows editing + schedule change
1
2
6
Bradley is expertly triggering me, but you know some enterprise architects are going to go partial abstract generic class factory factory iterator with this
3
0
19
At C#'s current trajectory, F# will be the more intuitive / instantly readable language within 3 years
24
2
139
It's also automatically distribute-able too, like the paid tiers of HangFire
0
0
2
This will be a lot easier to done once we have source-genned serialization implemented in v1.6
1
0
2
I have the beginnings of a HangFire replacement here if I abstracted away the actor bits, which is doable. 1. Have a general purpose IScheduledTask interface that defines a job with some input parameters 2. Create a dashboard that tracks tasks / allows editing + schedule change
Built a durable reminders / "distributed scheduler" system for Akka .NET actors yesterday. Wanted to use it for handling recurring billing and the multitude of deadline-driven edge cases that appear there. Client side invocation looks like this
4
1
30