or subscribe with
Join 19,300+ readers for one email each week.
Digests » 218
The O'Reilly Velocity Conference is returning to New York City, September 30-October 3—and just wait until you see who will be there: Alice Goldfuss (Site Reliability Engineer, GitHub), Casey Rosenthal (CTO, Backplane), Seth Vargo (Developer Advocate, Google), plus another 72 experts and thoughtleaders. And that's just the speakers. Velocity attendees are a pretty fascinating bunch, too. Don't miss this unique opportunity to discuss the latest in DevOps, Systems Engineering, and Infrastructure with those working on the front lines. Use code CDIG20 to save 20% on your Gold, Silver, or Bronze pass. That's a savings of up to $599 when you register during Early Price, now through August 17!
this week's favorite
Serverless is the evolution of cloud platforms in the direction of pure cloud native code. Serverless brings developers closer to business logic while insulating them from infrastructure concerns. It's a pattern that doesn't imply "no server" but rather, "less server." Serverless code is event-driven. Code may be triggered by anything from a traditional HTTP web request to a timer or the result of uploading a file. The infrastructure behind serverless allows for instant scale to meet elastic demands and offers micro-billing to truly "pay for what you use." Serverless requires a new way of thinking and approach to building applications and isn't the right solution for every problem.
With your kind permission, I'd like to deviate from our previously advertised agenda, and instead talk about a library by my colleague David Haney - SimplSockets. What I hope to convey is a range of both the reasoning behind prefering pipelines, but also practical guidance that the reader can directly transfer to their own IO-based needs.
A few months ago I put together a simple starter project for ASP.NET authorisation without any dependencies or configuration setup requirements. The motivation was my frustration with the complexity of the tutorials for something that should really be quite simple. I did leave the token based authorisation only partially complete however - there was no refresh token included which was an oversight on my part. Anyhow, I’ve gone ahead and done this plus a few other changes.
In the second post of .NET Internals series, we’re going to investigate the organization of .NET process’s memory. We’ll see what is stack and heap and what kind of data is stored on each of these memory structures.
Main focus for this release was on the open-source transition, but Xenko 3.0 also includes some new features, such as a switch to the new C# project system, video, hair and skin rendering. Read the full release notes here.