Hi, I test my post

Hi, I test my postHi, I test my postHi, I test my postHi, I test my postHi, I test my postHi, I test my postHi, I test my postHi, I test my postHi, I test my post

Hi, I test my post

Hi, I test my post

Hi, I test my post

Hi, I test my post

Hi, I test my post

REST vs SOAP ?

The main difference between these two approaches is the way that the service state is maintained. Do not think of the service state as the application or session state; instead, think of it as the different states that an application passes through during its lifetime. With SOAP, movement through different states can be accomplished through interaction with a single service endpoint, which may encapsulate and provide access to many operations and message types. With REST, a limited set of operations is allowed, and these operations are applied to resources represented and addressable by URIs (HTTP addresses). The messages capture the current or required state of the resource

+ SOAP is a protocol that provides a basic messaging framework upon which abstract layers can be built, and is commonly used as an RPC framework that passes calls and responses over networks using XML-formatted messages.

+ SOAP handles issues such as security and addressing through its internal protocol implementation, but requires a SOAP stack to be available.

+ REST is a technique that can utilize other protocols, such as JavaScript Object Notation (JSON), the Atom publishing protocol, and custom Plain Old XML (POX) formats.

+ REST exposes an application and data as a state machine, not just a service endpoint. It allows standard HTTP calls such as GET and PUT to be used to query and modify the state of the system. REST is stateless by nature, meaning that each individual request sent from the client to the server must contain all of the information necessary to understand the request since the server does not store
the session state data.

Microsoft .NET: Architecting Applications for the Enterprise - Free E Book download

Microsoft .NET: Architecting Applications for the Enterprise (PRO-Developer) (Paperback) - Free version from Microsoft
ISBN: 073562609X
http://www.microsoft.com/downloads/details.aspx?FamilyID=ce40e4e1-9838-4c89-a197-a373b2a60df2&DisplayLang=en

*** What is software architect?
- Software application architecture is the process of defining a structured solution that meets all of the technical and operational requirements, while optimizing common quality attributes such as performance, security, and manageability. It involves a
series of decisions based on a wide range of factors, and each of these decisions can have considerable impact on the quality, performance, maintainability, and overall success of the application.

NUnit - How to do Unit Test for C#

1. Download the msi version of NUnit on http://www.nunit.org/index.php?p=download
2. Read the Quick Start Guide http://www.nunit.org/index.php?p=quickStart&r=2.5.3

Sample Code will be available soon.

Five major stages of architecture design process

1. Identify Architecture Objectives. Clear objectives help you to focus on your architecture and on solving the right problems in your design. Precise objectives help you to determine when you have completed the current phase, and when you are ready to move to the next phase.

2. Key Scenarios. Use key scenarios to focus your design on what matters most, and to evaluate your candidate architectures when they are ready.

3. Application Overview. Identify your application type, deployment architecture, architecture styles, and technologies in order to connect your design to the real world in which the application will operate.

4. Key Issues. Identify key issues based on quality attributes and crosscutting concerns. These are the areas where mistakes are most often made when designing an application.

5. Candidate Solutions. Create an architecture spike or prototype that evolves and improves the solution and evaluate it against your key scenarios, issues, and deployment constraints before beginning the next iteration of your architecture

Domain Driven Design

Domain Driven Design (DDD) is an object-oriented approach to designing software based on the business domain, its elements and behaviors, and the relationships between them. It aims to enable software systems that are a realization of an underlying business domain by defining a domain model expressed in the language of business domain experts. The domain model can be viewed as a framework from
which solutions can then be rationalized.

Why .NET 3-tier architect or n-tier architect?

The main benefits of the N-tier/3-tier architectural style are:


+ Maintainability: Because each tier is independent of the other tiers, updates or changes can be carried out without affecting the application as a whole.

+ Scalability: Because tiers are based on the deployment of layers, scaling out an application is reasonably straightforward.

+ Flexibility: Because each tier can be managed or scaled independently, flexibility is increased.

+ Availability: Applications can exploit the modular architecture of enabling systems using easily scalable components, which increases availability.