Put the knife down and take a green herb, dude. (c) Ruffin Bailey 2001-2021

NOTE: Some of the links aren't the full URL in text, but they are in href for the link tag. Shortened so they wouldn't extend the blog template.

Note to self on your recent MVC recommendations: Don't forget caching/data persistence. I think caching's the only thing the conventional library-crazy MVC overhead[1] gets you "for free" that's worth saving, but it is worth saving. Our cache was used an absolute ton in the big-ish system I hacked on in the previous job.
Need to look at something like these...
http://stackoverflow.com/a/349111/1028230 (is missing locking on write/null cache)
http://stackoverflow.com/a/21269643/1028230 (has locking)
http://deanhume.com/home/blogpost/memcached-for-c----a-walkthrough/62
http://www.25hoursaday.com/...ASPNETCachingVsMemcached....aspx
(hello, old and uncomplicated. Note that almost all of these have magic strings of some sort, which is Wrong.)
http://www.javalobby.org/java/forums/t48846.html
http://dotnetslackers.com/.../...Comparison-of-Entity-Framework-and-NHibernate-2nd-Level-Caching.aspx
http://docs.jboss.org/hibernate/orm/4.3/manual/en-US/html/ch20.html#performance-fetching (man, that's tuned towards large, complex, multi-associative (ha) entities)
... but within the context of this...
http://mvcbloggers.blogspot.com/2013/05/redis-vs-memcached.html
Guessing this probably ultimately wins:
https://github.com/StackExchange/StackExchange.Redis
Also interesting...
http://hawkins.io/2012/07/advanced_caching_part_1-caching_strategies/
https://signalvnoise.com/posts/3113-how-key-based-cache-expiration-works
... though with the second I was left wondering something similar to what this guy was...
http://stackoverflow.com/questions/10774738/key-based-cache-expiration
[1] That is, the benefits of a "typical MVC stack" like I was using previously: SQL Server to NHibernate with MemCache, Repository model to access NHibernate, QueryOver, and your typical MVC/MVVM setup on the other side. I want to kill off NHibernate, QueryOver, and use of the Repository model. The only baby in the bath is caching. Though, wow, caching is easier when you have a 1-to-1 and onto relationship between Views and queries. I'm not saying that makes things smarter, but it does reduce the caching complexity.

Labels: caching, coding, mvc

title: Put the knife down and take a green herb, dude.	descrip: One feller's views on the state of everyday computer science & its application (and now, OTHER STUFF) who isn't rich enough to shell out for www.myfreakinfirst-andlast-name.com Using 89% of the same design the blog had in 2001.
FOR ENTERTAINMENT PURPOSES ONLY!!! Back-up your data and, when you bike, always wear white. As an Amazon Associate, I earn from qualifying purchases. Affiliate links in green.
x MarkUpDown is the best Markdown editor for professionals on Windows 10. It includes two-pane live preview, in-app uploads to imgur for image hosting, and MultiMarkdown table support. Features you won't find anywhere else include... MarkUpDown Multiline Table & Bootstrap Grid support. Beautiful Easy Actions that keep the Markdown flowing. HTML paste to paste HTML source into your documents. You've wasted more than $15 of your time looking for a great Markdown editor. Stop looking. MarkUpDown is the app you're looking for. Learn more or head over to the 'Store now!

Tuesday, March 31, 2015
Don't forget your cache, self NOTE: Some of the links aren't the full URL in text, but they are in href for the link tag. Shortened so they wouldn't extend the blog template. Note to self on your recent MVC recommendations: Don't forget caching/data persistence. I think caching's the only thing the conventional library-crazy MVC overhead[1] gets you "for free" that's worth saving, but it is worth saving. Our cache was used an absolute ton in the big-ish system I hacked on in the previous job. Need to look at something like these... http://stackoverflow.com/a/349111/1028230 (is missing locking on write/null cache) http://stackoverflow.com/a/21269643/1028230 (has locking) http://deanhume.com/home/blogpost/memcached-for-c----a-walkthrough/62 http://www.25hoursaday.com/...ASPNETCachingVsMemcached....aspx (hello, old and uncomplicated. Note that almost all of these have magic strings of some sort, which is Wrong.) http://www.javalobby.org/java/forums/t48846.html http://dotnetslackers.com/.../...Comparison-of-Entity-Framework-and-NHibernate-2nd-Level-Caching.aspx http://docs.jboss.org/hibernate/orm/4.3/manual/en-US/html/ch20.html#performance-fetching (man, that's tuned towards large, complex, multi-associative (ha) entities) ... but within the context of this... http://mvcbloggers.blogspot.com/2013/05/redis-vs-memcached.html Guessing this probably ultimately wins: https://github.com/StackExchange/StackExchange.Redis Also interesting... http://hawkins.io/2012/07/advanced_caching_part_1-caching_strategies/ https://signalvnoise.com/posts/3113-how-key-based-cache-expiration-works ... though with the second I was left wondering something similar to what this guy was... http://stackoverflow.com/questions/10774738/key-based-cache-expiration [1] That is, the benefits of a "typical MVC stack" like I was using previously: SQL Server to NHibernate with MemCache, Repository model to access NHibernate, QueryOver, and your typical MVC/MVVM setup on the other side. I want to kill off NHibernate, QueryOver, and use of the Repository model. The only baby in the bath is caching. Though, wow, caching is easier when you have a 1-to-1 and onto relationship between Views and queries. I'm not saying that makes things smarter, but it does reduce the caching complexity. Labels: caching, coding, mvc posted by ruffin at 3/31/2015 05:41:00 PM

<< Older \| Newer >>