The World According to LINQ

http://queue.acm.org/detail.cfm?id=2024658

RELATED READING

1. C# Query Expression Translation Cheat Sheet; http://bartdesmet.net/blogs/bart/archive/2008/08/30/c-3-0-query-expression-translation-cheat-sheet.aspx

2. Comprehensions with Order by and Group by; http://research.microsoft.com/en-us/um/people/simonpj/papers/list-comp/index.htm

3. Expressions; http://www.cs.cmu.edu/Groups/AI/html/r4rs/r4rs_6.html#SEC28

4. Google Chart API; http://code.google.com/apis/chart/image/

5. Hadoop; http://hadoop.apache.org/

6.JavaScript;
https://developer.mozilla.org/en/JavaScript/Guide/Predefined_Core_Objects#Array_comprehensions

7. LINQ; http://msdn.microsoft.com/en-us/netframework/aa904594

8. LINQ to HPC;
http://blogs.technet.com/b/windowshpc/archive/2011/07/07/announcing-linq-to-hpc-beta-2.aspx

9. Monads; http://en.wikipedia.org/wiki/Monad_%28functional_programming%29

10. Parallel Programming with .NET; http://blogs.msdn.com/b/pfxteam/archive/2010/04/04/9990343.aspx

11. Python; http://www.python.org/dev/peps/pep-0289/

12. Rx (Reactive Extensions); http://msdn.microsoft.com/en-us/data/gg577609

13. Scala; http://www.scala-lang.org/node/111

14. Xamarin; http://xamarin.com/ 

Read More

MCPD

Read More

MemoryImage

From: http://martinfowler.com/bliki/MemoryImage.html

When people start an enterprise application, one of the earliest questions is "how do we talk to the database". These days they may ask a slightly different question "what kind of database should we use - relational or one of these NOSQL databases?". But there's another question to consider: "should we use a database at all?"

One of the defining characteristics of enterprise applications is the need to store long term data, which naturally leads people to reach for a database. After all persisting data is one of the main things databases do. Using a memory image is a different route to persistence that doesn't involve a database.

The key element to a memory image is using event sourcing, which essentially means that every change to the application's state is captured in an event which is logged into a persistent store. Furthermore it means that you can rebuild the full application state by replaying these events. The events are then the primary persistence mechanism.

Read More