Group items tagged

"Lately I've been talking a lot about rich client applications written in HTML and JavaScript. These are frequently referred to as "SPAs" (Single Page Applications). I call them SPAs myself - it's cute and flows easily off the tongue. Unfortunately the phrase "single page application" badly misrepresents the true nature of this architectural style."

CQRS, while a relatively simple concept, still brings a lot of assumptions about what CQRS is and should be. So what is CQRS? Simply put, CQRS is two objects where there was once one. We're splitting code infrastructure down to the data layers between commands and queries. But the assumptions around what a CQRS should be lead folks I've seen down paths of unnecessary complexity. Complexity around the architecture, and especially around the UI.

Roy Fielding writes a PhD dissertation describing the architectural style of the World Wide Web. He coins the term 'Representational State Transfer' (REST) to describe it - after all, if you're going to talk about something, you need to give it a name. Somehow, in a semantic shift of epic fail proportions, the term REST has also come to mean something completely different to most people, a 'style' of writing web services. This style has no agreed protocol.

"This is the first of a two-part series that will tell the long story of the C# memory model. The first part explains the guarantees the C# memory model makes and shows the code patterns that motivate the guarantees; the second part will detail how the guarantees are achieved on different hardware architectures in the Microsoft .NET Framework 4.5."

"We've been working with, building, and evangelising message queues for the last year, and it's no secret that we think they're awesome. We believe message queues are a vital component to any architecture or application, and here are ten reasons why:"

"But even in today's SW industry, there does not seem to be much of an expectation from SW professionals that we should have the 'capability/tools to build our own tools' that do much of the project work for us. I am not talking about the simple automation, things like rename/refactor or autocorrect, or intellisense and all that, I am talking about the kind of automation and tooling that writes or deploys software for us and saves hours, days and weeks of our time from handcrafting software solutions from scratch again."

"Dependencies are nearly unavoidable for non-trivial software projects. These can be large dependencies, such as web frameworks and databases, or smaller decisions, such as pagination helpers or simple math libraries. The inevitable inclusion of these dependencies, however, is not an excuse to shape the solutions of your system around what you do not own. Instead, there ought to be an emphasis on finding the right fit and then owning the way dependencies interface with your system."

"Because frameworks are so good at making decisions for us, we get lazy. Instead of thinking hard about how to build a clean system with crisp abstractions, we think about what the framework would want us to do, regardless of whether the resulting code is clean."

The Microsoft .NET platform, originally introduced in 2002, is mature and it provides developers with great options for creating software that can meet the requirements of any project. With many options, though, it can be difficult for today's .NET developer to choose the correct .NET technologies for a project. Addressing this problem, Telerik has assembled its senior technical leaders to produce the Microsoft Platform Guidance 2012. This document attempts to provide prescriptive guidance for .NET developers trying to determine the best .NET technologies to use for specific software challenges.

"This article aims to describe why I think that DDD aids you tremendously in creating robust and flexible applications."

"Microsoft StreamInsight consists of a set of programming tools, and most of what is written about StreamInsight is written specifically for programmers. But what if you are, for example, a database administrator or data analyst without an extensive programming background? You're wondering if StreamInsight might be a solution for a problem you have, but the existing documentation leaves you scratching your head."

One of the mistakes I see people make (and have made myself) is assuming that you must choose exactly one ORM strategy for an entire database/application/system. It's simply not the case.