NinethSense

How to use the Autoscaling Application Block.

The Autoscaling Application Block can automatically scale your Windows Azure application based on rules that you define specifically for your application.

URL: http://www.windowsazure.com/en-us/develop/net/how-to-guides/autoscaling/

My new posts on Enterprise, Solution and Technical Architecture and study notes on TOGAF will be continued on my new blog http://arch.ninethsense.com/.

I have moved all the existing posts from my technical blog to the new place except which few shown errors while exporting and importing. For that particular reason, I will be keeping my existing blog posts in architecture category.

Thank you for all my followers and reader for the support.

• Single Responsibility Principle
• Open Closed Principle
• Liskov Substitution Principle
• Interface Segregation Principle
• Dependency Inversion Principle

A good read here.

The main objective of The Good enough Architecture MEthodology is to create a good enough ground for an IT solution (one solution or a whole IT portfolio) by using methods and best practices for gathering and analysing the adequate requirements that enable the design, development and establishment of a good enough architecture.

More reading here.

Intro to GAME pdf.

Here is an interesting read on this topic – http://genehughson.wordpress.com/2011/12/07/so-what-exactly-does-an-architect-do/

Enforce Coding Standards with Code Analysis?

Video Link

Few good readings here, here, here and here.

Here are few interesting articles for reading:

1. The Psychology of Reviews: Distinction Bias, Evaluability Hypothesis and the Framing Effect
2. Model Reviews: Best Practice or Process Smell?
3. Gods and Mortals, Part 1

The CQRS pattern and event sourcing are not mere simplistic solutions to the problems associated with large-scale, distributed systems.

This pattern says “Every method should either be a command that performs an action, or a query that returns data to the caller, but not both.”

You can download a book “Book Download: Exploring CQRS and Event Sourcing” for free from here.

Detailed reading: http://martinfowler.com/bliki/CQRS.html

Wiki: http://en.wikipedia.org/wiki/Command-query_separation

The .NET Persistence API, is a persistence and Object Relational Mapping (ORM) specification for the .NET framework which contains the classes and interfaces that define the contracts between client applications which require persistence and ORM services and the vendors which provide them.

.NET Persistence API is the .NET equivalent for the java JPA framework and is based on it. It offers the same standard for managing relational data in applications using the .NET framework written in C#, Visual Basic and other .NET languages.

More reading here – http://www.npersistence.org/.

NHibernate implements NPersistence.

NPersistence layer requires .Net 4.0 platform.

Download the NPersistence zip file at this website’s download page, extract it and copy the ‘NPersistence.dll’ file to your application’s development location.