eric.polerecky.com

Keynote: Ted Neward – Rethinking the enterprise

• the brain is hardwired to use what you know. creatures of habbit.
• All software sucks. It just sucks in different ways.
• See Tweets

Hanselman – Web of love

• WebAPI is some good. GetP
• Mobile theme support using xxxxxx.mobile.cshtml
• IsMobile, _LayoutSwitcher.cshtml for switching between mobile/desktop

What’s new in ASP.NET MVC4

• demos of jquery mobile theme support – all css that comes with jquery mobile. modify theme is the easiest way to change them.
• support for anything.mobile.cshtml works at the partial level.
• knockoutjs included by default. designed for single page apps (gmail, todolists)
• jquery mobile included by default.
• Install-Package MvcJQueryMobile
• Recipes:
  • Install via nuget
  • Mvc.Haack.ViewMobilizer – sample
• async and await
  • .net 4.5 (download CTP)
  • inherit from asyncController
  • public async Task<ViewResult> Index
  • Uses same thread if possbile
• Guess: another preview release of MVC4 (soon)
• stevesmithblog.com

Wicked Domain Models

• Anemic Domain Models.
• Managers->Serivces->PageLoad->Back to Services->Utility->Helper->etc.
• services should be used to merge data access and domain logic.
• don’t expose things that are not supported ex: raw collection w/ add/remove/clear list.
• when a collection is just queryable expost it as ienumberable. not icollection or ilist.
• is object has required fields make constructor that requires information (paramaters) . If a object does not have required information do not use a constructor with params.
• The object model should only expose as much functionallity as is required.
• If values can’t change after assignment put assignment as part of the ctor.
• DDD – Double Dispatch (taking a service using it by passing myself (this) in)
• slutty code – one thing cares too much about another and keeps poking it.
• Talking to yourself is good
• Methods should be in your domain model. Methods are good for your domain model.
• DDD = name of the game is make it private.
• Stratagy Pattern = removing switch statems for actual logic.
• Services are part of DDD, they coordinate and delegate to model.
• by pushing functionality down to the model you remove the requirement for intrinsic knowledge in someones head of a systems architecture.
• Object model should be behavioral, DTO = null.

Massive Scailability thru ruthless caching

• AppFabric Demo
  • authoritative information is expensive.
  • the network is a huge cost.
  • Added a micro-cache (5sec) commonly eliminates 95% of database calls.
  • AppFabric cache is a “aside” cache. You check the cache for the data first, if not exist get from source (db, web service, etc)
  • AppFabric is a service, runs on a port, you connect to it.
  • Unique named caches
  • Connect to the cache much like a database.
  • Connect localhost?

Collections DeepDive

• Adding an element to an array using .Add() does Array.Copy(). O(n). Array.Copy() is slow. Use AddRange(). No loops.
• Using Array.Add() on less then 10K objects is fine…if you will never scale.
• Get a copy of ILSpy to understand what is happening at a lower level.
• LinkedList<T> is fast, you have to tell it where to put an item but slow on look ups. (after for add/remove)
• Dictionary gives fast lookup. Performances depends on GetHashCode
• Use int/string for key. It’s the fastest and already optimized.
• For multi-value per key use .ToLookup – this is cool.
• Sorted Collections
• SortedList<T> uses less memory than SortedDictionary<T>
• SortedDictionary<T> has fast add/remove and is sorted.
• Adding lots of data at once use Sorted<T> (via AddRange())
• Concurrent Collections
• ConcurrentBag,Dictionary,Queue,Stack,Partitioner,BlockingCollection
• TryAdd() – returns bol
• TryTake() – returns bool
• Always check value before moving on.
• BlockingCollection<T>
• Blocks and waits until TryXXXX is done.
• TryXXXX can specify a timeout.

Unit of work!!!!! – Business logic should not have to care about saving information.