I really liked this post! I'm a Full Stack .NET Developer and I make ASP.NET Web Core API's, and I know how much API's can get very complex. And RIP this is something that nobody even sees, the people only look at frontend.
What you could add maybe is talking about
optimization. methaphor could be how macdonald can serve so quickly and thus can increase amount of client per chef
API Key for when other restaurants could benefit of your restaurants, you can limit it, track how much you helped and more
Testing. like unit tests and other type of tests, see if a dish taste good before putting in menu
Maintenance. updating depedencies, so if a ingredient is expired not good to consume anymore, vulnerabilitie cause get client sick.
Versioning. if you have a lifetime access for food you sold before, but then realized it was a very bad idea so discountinue it (no way to buy it), but people who already bought the lifetime access should still be able to use it or they will go to court.
Documentation. like if you let people cook their meat in their seat like some restaurant do, then a paper on the table showing the steps on how to do it.
Analysis. like with posthog
Orchestration with like .NET Aspire.
scaling, not like load balancing and horizontal scaling alone, but more like with k8s
compliancie to like conform to the gdpr. or to never leak the sensitive info in logs annotate with nuget packages the fields.
developer/stagging/production envirement. when in developer envirement when testing don't count the made dishes as sold for analysis for exemple. (like having multiple different implementation of same interface, depending on envirement)
...
and much more!
Very inspirational! (meaning I want to also post now as good as you do!)
Thank you ❤️ - I absolutely loved your ideas as well! I’ve just started writing recently, so I hope you start too, and I’ll be keeping an eye out for your posts. 😜
Thanks for this post. I'm very new to being a full-stack developer, going on 6 months, and this was very helpful. Thanks for the analogies and what to look out for in the future for scaling.
That's underrated.
Thanks.
Glad you think so! Appreciate you dropping by 🙌
By the way, using a message queue for serving... a real queue (orders) is an educational metaphor, right?
Yep! Thought it’d make the idea of queues feel a bit more real 😄
I really liked this post! I'm a Full Stack .NET Developer and I make ASP.NET Web Core API's, and I know how much API's can get very complex. And RIP this is something that nobody even sees, the people only look at frontend.
What you could add maybe is talking about
Very inspirational! (meaning I want to also post now as good as you do!)
Thank you ❤️ - I absolutely loved your ideas as well! I’ve just started writing recently, so I hope you start too, and I’ll be keeping an eye out for your posts. 😜
Really everything I needed to know
great information
Thank you! Glad you found it helpful 🙌
straight to the point, i like it
Appreciate it! That’s the vibe I’m going for 😎
Thanks for this post. I'm very new to being a full-stack developer, going on 6 months, and this was very helpful. Thanks for the analogies and what to look out for in the future for scaling.
Thank you! Glad you found it helpful 🙌
Thanks for sharing ! Your examples and explainations are really clearly and helpful.