Digests » 198
this week's favorite
For brevity, in this post, I will not document how to build out the backend ASP.NET Core project used in this demo as the code and procedure are identical to the previous post. So, if you're interested in the nuts and bolts of the code and steps required to enable token authentication and authorization in ASP.NET Core go check that post out first (tip: it's the first half of the post up until the frontend starts at The Angular app section). In this post, I will focus solely on the bits required to secure your Vue.js application using client-side token-based authentication. 🔐
It took 10 minutes to set up App Insights. It took two days (and work continues) to fix what it found. I love it. This tool has already given me a deeper insight into how my code runs and how it's behaving - and I'm just scratching the service. I'll need to do some videos and/or more blog posts to dig deeper. Truly, you need to try it.
Span<T> and Memory<T> are new features in .NET Core 2.1 that allow strongly-typed management of contiguous memory, independently of how it was allocated. These allow easier to maintain code and greatly improves the performance of applications by reducing the number of required memory allocations and copies.
As it turns out, there are many practical benefits to making your types immutable—not just the value objects. I remember the first time I came across the concept of immutable types. I was researching string immutability, and somehow Google led me to a Stack Overflow question about immutability in general.
Carrying on from the last post in this series on creating performant and scalable web APIs using ASP.NET Core, we’re going to continue to focus on caching. In this post we’ll implement a shared cache on the server and clean the code up so that it can be easily reused.