.NET food for the brains!

from Coding Blocks .NET , on 8/27/2016 , played: 906 time(s)

Storing smaller subsets of data in a faster, closer memory can make astronomical differences in performance. This episode we're talking about the caching tools and techniques that application frameworks provide. The original version of the shownotes can be found at: http://www.codingblocks.net/episode46 New Poll! Podcast News Thanks for the reviews! Mr_Automation, Nateve, chubb5000, Travelerbell, LaCaren, ryanwebjackson, LuckyCoding SwanseaCon 2016 is coming up, September 12th - 13th in South Wales http://swanseacon.co.uk/ We have tickets to give away, tweet us at @CodingBlocks with the hashtag #SwanseaCon if you want to go!!! Awesome sounding topics like…Refactoring and Code Smells, 10x Developer Myth and Jurassic Park to Microservices Save yourself £450.00!! Reddit has been kind, Thank you so much! https://www.reddit.com/r/programming/comments/4z6r3v/my_top_eight_mustlisten_developer_podcasts/ Great comments on the last (and really, all) episode: www.codingblocks.net/episode45 Russell Hammet: Grace Hopper discussing, visualizing nanoseconds Carole Anne, always great perspective on our poll - and how discimination can masquerade as other things - great tie in with impostor syndrome Jeremy Shannon: Low Level Details for High Level Developers : https://docs.google.com/presentation/d/1azqLjBh2U0V5_-w_SXi6vDC8uiRq6VNW1s_-2B2Kho4/edit?usp=sharing Amazon wants to ship your package before you actually buy it! (example of temporal locality) http://blogs.wsj.com/digits/2014/01/17/amazon-wants-to-ship-your-package-before-you-buy-it/ Intel and Micron’s memory breakthrough - 3D Xpoint http://www.intel.com/content/www/us/en/architecture-and-technology/non-volatile-memory.html https://twit.tv/shows/security-now/episodes/573?autostart=false Meetups on ReactJS + Elixir + RethinkDB, and Reactive apps Topic: Caching in your Application Framework Last episode, we talked about hardware latency numbers that “all programmers should know” Relative speeds of cpu to sending packets to the other side of the world…300 million times slower! Storing smaller subsets of data in a faster, closer memory can make astronomical differences Knowing these numbers help you make smart architectural decisions about your app, For example - if you expect you’re traffic to come in quicker than your data changes, or if you don’t care about showing up-to-date data - you can get your data 600x faster by fetching it from RAM then from the internet! Speed is important, both for UX - but also because the quicker you can handle requests * The less resources you need $$$ Today, we’re going to focus in on the types of caching that you can make use of as a programmer We’re going to do this by focusing in on one specific framework: ASP.Net DON’T WORRY - If you’re not a Microsofty!!! The techniques we’re talking about are similar to caching you’ll see in other frameworks and languages - we just wanted to choose something we’re familiar with ASP.NET and Application Caching Overview What is ASP.NET? Open-Source framework for creating web applications and web services Provides tools for dealing with web requests, responses, sessions, cookies, as well as utilities for writing html Works in conjunction w/ .Net, which provides abilities like system I/O, networking, everything else When would you use ASP.NET over…NodeJs, RoR, PHP, etc When would you NOT choose ASP.NET? When it comes to writing ASP, there are a two major sides to it: HTML Templating: Razor, DotLiquid Compiled language: C#, VB, F#, Any .NET language Framework provides a couple types of caching to the programmer: Application cache, page output cache, and attribute caching Loads of other caching going on underneath the covers, GAC, Nuget, etc - but we’re focused on ASP.Net Benefits of caching in the application Reduce database/service loads



blog comments powered by Disqus