How many failing requests have you sent before you have dug yourself through swathes of error messages and documentation to get to that one penultimate successful request making your heart sing and fists shaking in the air? Just think about your first interaction with an API. What this means is that without great, user-friendly error messages, your API is not going to be great.

Link: What’s Your Problem? – Asbjørn UlsbergĪ talk given by Asbjørn Ulsberg from PayEx at the 2019 Platform Summit in Stockholm.Īn API isn’t stronger than its weakest link and what’s often ignored in the ongoing maintenance and development of an API is the constant effort required to provide great self-servicable error messages. I’ve blogged Co-Hosting Orleans and ASP.NET Core which this about this feature.Ī tool that helps you find transitive package references that can be removed.Ĭastle.Core (ref by Baz) 4.4.0 <- 4.3.1 (Baz) I was happy to see the generic host for co-hosting with something like ASP.NET Core. A BIG Thank You to all who contributed to this release in various ways! These changes were driven by the experience of many people running Orleans-based applications in production in a wide range of scenarios and environments, and by the ingenuity and passion of the global Orleans community that always strives to make the codebase better, faster, and more flexible. A great number of improvements and fixes went in, as well as several new features, since Orleans 2.0. We are excited to announce the Orleans 3.0 release. Follow on Twitter Introducing Orleans 3.0 Let me know in the comments or on Twitter. I’d love to hear what you found most interesting this week. Here are the things that caught my eye recently in.

Sponsor: Do you build complex software systems? See how NServiceBus makes it easier to design, build, and manage software systems that use message queues to achieve loose coupling.

Snitch software