"The following tutorial guides you through the steps required to create a basic Service Bus for Windows Server application, and contains the following steps:"
" The Xcoordination Application Space is a small framework to make writing asynchronous and distributed applications easier. It´s based on the concept of Space Based Computing which revolves around the notion of autonomous functional units communicating only indirectly and possibly in a stateful manner."
" Concurrency and Coordination Runtime (CCR) is a managed code library, a Dynamically Linked Library (DLL), accessible from any language targeting the .NET Common Language Runtime (CLR).
The CCR addresses the need of service-oriented applications to manage asynchronous operations, deal with concurrency, exploit parallel hardware and deal with partial failure. It enables the user to design applications so that the software modules or components can be loosely coupled; meaning they can be developed independently and make minimal assumptions about their runtime environment and other components. This approach changes how the user can think of programs from the start of the design process and deals with concurrency, failure and isolation in a consistent way."
" Expanding on the topic of "are you kidding me"... one of the MOST PREVALENT problems I see today is the dreaded "GUIDs as PKs" problem. However, just to be clear, it's not [as much of a] problem that your PRIMARY KEY is a GUID as much as it is a problem that the PRIMARY KEY is probably your clustering key. They really are two things BUT the default behavior in SQL Server is that a PRIMARY KEY uses a UNIQUE CLUSTERED INDEX to enforce entity integrity. So, I thought I'd take this post to really dive into why this is a problem and how you can hope to minimize it. "
"This new toolset and approach will revolutionize the way individuals and organizations: design, build and deploy their repeatable solutions by capturing, incorporating and scaling-out their best practices, knowledge and expertise to increase the consistency, predictability, supportability and maintenance of solutions they deliver. "
"Domain Driven Design (DDD) is an approach of how to model the core logic of an application. The term itself was coined by Eric Evans in his book "Domain Driven Design". The basic idea is that the design of your software should directly reflect the Domain and the Domain-Logic of the (business-) problem you want to solve with your application. That helps understanding the problem as well as the implementation and increases maintainability of the software."
Awesome article!
"The most exciting engineering challenges lie on the boundary of theory and the unknown. Not so unknown that they're hopeless, but not enough theory to predict the results of our decisions. Systems at this boundary often rely on emergent behavior - high-level effects that arise indirectly from low-level interactions."
" Performance is a topic of increasing importance in the software industry. Today performance engineers and architects as well as operations people have to ensure that complex application landscapes works seemlessly and problems are resolved fast and with minimal effort. "
"Gabriel Schenker's excellent series of posts on "How we got rid of the database" offers a great insight on the benefits of a CQRS/ES application. One of the problems often seen with designing user interfaces that introduce eventual consistency into the mix is how to present this new paradigm to the end user. But whether we've thought or not, eventual consistency is all around us, as Gabriel points out in a few examples:"
"Why are so many sites vulnerable to these well-known holes? Probably because it's insanely hard for programmers to solve the fundamental "strings problem" at the heart of these vulnerabilities. The problem itself is easy to understand, but we humans aren't equipped to carry out the solution. Simply put, we just plain suck at keeping a bazillion different strings straight in our heads, let alone consistently and reliably rendering their interactions safe whenever they cross paths in a modern web application. It's easy to say, "just escape the darn things," but it's hard to get it right, every single time."
" I would be willing to place a bet that most computer programmers have, on multiple occasions, expressed an opinion about the desirability of certain kinds of type systems in programming languages. Contrary to popular conception, that's a great thing! Programmers who care about their tools are the same programmers who care about their work, so I hope the debate rages on. "
"PetaPoco is a tiny, fast, single-file micro-ORM for .NET and Mono.
Like Massive it's a single file that you easily add to any project
Unlike Massive it works with strongly typed POCO's
Like Massive, it now also supports dynamic Expandos too - read more
Like ActiveRecord, it supports a close relationship between object and database table
Like SubSonic, it supports generation of poco classes with T4 templates
Like Dapper, it's fast because it uses dynamic method generation (MSIL) to assign column values to properties"
"Bad data always seems to appear when, and where, one least expects it. Sam explains the great value of a defensive approach based on constraints to any team that is developing an application in which the data has to be exactly right, and where bad data could cause consequential severe financial damage. It is perhaps better seen as creating a test-driven database"
"This post reflects on the steps I needed to perform to create my first Windows Identity Foundation (WIF) application from zero to Hello World. It can serve as a bootstrap for starting developing Claims-Aware ASP.NET application using Windows Identity Foundation (WIF). "
"Imagine a world where you don't have to worry about authentication. Imagine instead that all requests to your application already include the information you need to make access control decisions and to personalize the application for the user. "
"I began writing tests around 8 years ago and I must say this revolutionized my way of developing code. In this blog post, I'd like to group and share several non-trivial feedbacks gained over all these years of practicing real-world testing."
"Summary: In this paper we'll look at the new Entity Framework 4 that ships with .NET Framework 4 and Visual Studio 2010. I'll discuss how you can approach it's usage from a model-first perspective with the premise that you can drive database design from a model and build both your database as well as your data access layer declaratively from this model. The model contains the description of your data represented as entities and relationships providing a powerful approach to working with ADO.NET, creating a separation of concerns through an abstraction between a model definition and its implementation."
"SisoDb is a document-oriented db-provider for Sql-Server written in C#. It lets you store object graphs of POCOs without having to configure any mappings. Each entity is treated as an aggregate root and will get separate tables created on the fly."
"This site has been setup to replace the creaking and aging site at dddstepbystep.com, which for all it's plus points, was proving impossible to maintain. Sorry Community Server you had to go!"