ASP.NET MVC Evolution

MVC1	Basic version introduced by Microsoft
MVC2	Strongly typed html helpers Attribute based model validation scaffolding with customizable templates Fine-tune API and features
MVC3	Razor view engine Support for Multiple View Engines Support Data Annotations Model Validation Improvements Dependency Injection Improvements Global Action Filters New "ViewBag" Property Powerful hooks with Dependency Injection and Global Action Filters Rich JavaScript support with unobtrusive JavaScript, jQuery Validation, and JSON binding HTML 5 enabled project templates
MVC4	WebAPI Default project template Mobile project template (JQuery Mobile) Display Modes Task Support for Asynchronous Controllers Enhanced support for asynchronous methods Model binding Bundling and Minification Add Controller to any project folder release notes
MVC5	One ASP.NET ASP.NET Identity Bootstrap Authentication filters Filter overrides Attribute routing Concurrent Development Interface based architecture
MVC5.1.2	Attribute routing improvements Bootstrap support for editor templates Enum support in views Unobtrusive validation for MinLength/MaxLength Attributes Supporting the ‘this’ context in Unobtrusive Ajax
MVC5.2.2	Attribute routing improvements
MVC6 (Part of ASP.NET vNext) - (Not released yet...)	vNext = MVC, Web API, WebPage and SignalLr peices ASP.NET vNext uses the Roslyn Compiler Supports OWIN Run on hosts other than IIS Dependency injection Using the IServiceProvider interface we can easily add our own dependency injection container) Startup.cs instead of Global.asax Tag Helpers enable server-side code to participate in creating and rendering HTML elements in Razor files.

Design Patterns in Software Development

What are Design Patterns in Software Developemt?

"A pattern is a recurring solution to a problem in a context."
Design Patterns in object oriented world is reusable solution to common software design problems which occur again and again in real world application development. It is a template or description for how to solve a problem which can be used in many different situations.

Patterns are used by developers to their particular design to solve their problems. Patterns usage and choice to choose among different design patterns is based on individual need and their problem.

Defination on wikipedia

Classification

Design patterns were originally grouped into the categories: creational patterns, structural patterns, and behavioral patterns, and described using the concepts of delegation, aggregation, and consultation.

Creational patterns
Abstract factory	Provide an interface for creating families of related or dependent objects without specifying their concrete classes.
Builder	Separate the construction of a complex object from its representation, allowing the same construction process to create various representations.
Factory method	Define an interface for creating a single object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses (dependency injection).
Lazy initialization	Tactic of delaying the creation of an object, the calculation of a value, or some other expensive process until the first time it is needed. This pattern appears in the GoF catalog as "virtual proxy", an implementation strategy for the Proxy pattern.
Multiton	Ensure a class has only named instances, and provide a global point of access to them.
Singleton	Ensure a class has only one instance, and provide a global point of access to it.
following are not considered in (Creational) Design Patterns
Prototype	Specify the kinds of objects to create using a prototypical instance, and create new objects by copying this prototype.
Object pool	Avoid expensive acquisition and release of resources by recycling objects that are no longer in use. Can be considered a generalisation of connection pool and thread pool patterns.
Resource acquisition is initialization	Ensure that resources are properly released by tying them to the lifespan of suitable objects.
Object library	Encapsulate object management including factory interface with live and dead lists.
Structural patterns
Adapter or Wrapper or Translator	Convert the interface of a class into another interface clients expect. An adapter lets classes work together that could not otherwise because of incompatible interfaces. The enterprise integration pattern equivalent is the translator.
Bridge	Decouple an abstraction from its implementation allowing the two to vary independently.
Composite	Compose objects into tree structures to represent part-whole hierarchies. Composite lets clients treat individual objects and compositions of objects uniformly.
Decorator	Attach additional responsibilities to an object dynamically keeping the same interface. Decorators provide a flexible alternative to subclassing for extending functionality.
Facade	Provide a unified interface to a set of interfaces in a subsystem. Facade defines a higher-level interface that makes the subsystem easier to use.
Flyweight	Use sharing to support large numbers of similar objects efficiently.
Proxy	Provide a surrogate or placeholder for another object to control access to it.
following are not considered in (Structural) Design Patterns
Front controller	The pattern relates to the design of Web applications. It provides a centralized entry point for handling requests.
Marker	Empty interface to associate metadata with a class.
Module	Group several related elements, such as classes, singletons, methods, globally used, into a single conceptual entity.
Twin	Twin allows modeling of multiple inheritance in programming languages that do not support this feature.
Behavioral patterns
Chain of responsibility	Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it.
Command	Encapsulate a request as an object, thereby letting you parameterize clients with different requests, queue or log requests, and support undoable operations.
Interpreter	Given a language, define a representation for its grammar along with an interpreter that uses the representation to interpret sentences in the language.
Iterator	Provide a way to access the elements of an aggregate object sequentially without exposing its underlying representation.
Mediator	Define an object that encapsulates how a set of objects interact. Mediator promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.
Memento	Without violating encapsulation, capture and externalize an object's internal state allowing the object to be restored to this state later.
Observer or Publish/subscribe	Define a one-to-many dependency between objects where a state change in one object results in all its dependents being notified and updated automatically.
State	Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.
Strategy	Define a family of algorithms, encapsulate each one, and make them interchangeable. Strategy lets the algorithm vary independently from clients that use it.
Template method	Define the skeleton of an algorithm in an operation, deferring some steps to subclasses. Template method lets subclasses redefine certain steps of an algorithm without changing the algorithm's structure.
Visitor	Represent an operation to be performed on the elements of an object structure. Visitor lets you define a new operation without changing the classes of the elements on which it operates.
following are not considered in (Behavioral) Design Patterns
Blackboard	Artificial intelligence pattern for combining disparate sources of data (see blackboard system)
Null object	Avoid null references by providing a default object.
Servant	Define common functionality for a group of classes.
Specification	Recombinable business logic in a Boolean fashion.
following were not considered in originally grouped into the categories Design Patterns
Concurrency patterns
Join	Join-pattern provides a way to write concurrent, parallel and distributed programs by message passing. Compared to the use of threads and locks, this is a high-level programming model.
Lock	One thread puts a "lock" on a resource, preventing other threads from accessing or modifying it
Messaging design pattern (MDP)	Allows the interchange of information (i.e. messages) between components and applications.
Monitor object	An object whose methods are subject to mutual exclusion, thus preventing multiple objects from erroneously trying to use it at the same time.
Read-write lock	Allows concurrent read access to an object, but requires exclusive access for write operations.
Scheduler	Explicitly control when threads may execute single-threaded code.
Thread pool	A number of threads are created to perform a number of tasks, which are usually organized in a queue. Typically, there are many more tasks than threads. Can be considered a special case of the object pool pattern.
Architectural Design Patterns
Model-View-Controller
Presentation-abstraction-control
Model View Presenter
Model View ViewModel
Service-oriented architecture
Microservices
Blackboard system
Event-driven architecture
Implicit invocation
Layers
Multitier architecture (often three-tier or n-tier)
Naked objects
Operational Data Store (ODS)
Peer-to-peer
Pipe and filter architecture
Broker Pattern

List of software architecture styles and patterns

NoSql Databases

Hadoop

Is an entire ecosystem of integrated distributed computing tools, at the core of which are a file system (HDFS) and a programming framework (Map-Reduce).
Welcome to Apache™ Hadoop®!

Cassandra

Is a NoSQL data store based on a key-value pairing system, where value is then further structured into a columnar like store.
The Apache Cassandra Project

MongoDB

A NoSQL data store based on key-value pairing system where value is JSON documents. Has its own unique querying language.
MongoDB

CouchDB

A NoSQL data store based on key-value pairing system where value is JSON documents. Uses a combination of HTTP, Javascript, and map-reduce for querying.
Apache CouchDB

Cassandra, Mongo, and Couch arekey-value based NoSQL data stores in that way they are pretty similar .
Each noSql database have their advantages and disadvantages. If you're interested in one, you should probably at least have a good understanding of when to use one NoSQL vs another.


Hadoop is a huge in scope to learn than the others because it is comprised of many different components, including its own columnar (hBase) and SQL like data storage (Hive) platforms.

More info about nosql-database

Agile Software Development

What Is Agile?

Agile methodology is an alternative to traditional project management, typically used in software development. It helps teams respond to unpredictability through incremental, iterative work cadences, known as sprints. Agile methodologies are an alternative to waterfall, or traditional sequential development.

Manifesto for Agile Software Development

Agile Manifesto

Individuals and interactions
Working software
Customer collaboration
Responding to change

Twelve Principles of Agile Software

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity--the art of maximizing the amount of work not done--is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Agile Methodologies

• Scrum
• Lean
• Kanban
• Extreme Programming (XP)
• Crystal
• Dynamic Systems Development Method (DSDM)
• Feature-Driven Development (FDD)

List of Agile Methodologies on VersionOne website

prioritized task/stories using MoSCoW Rules:

• M-Must have
• S-Should have if at all possible
• C-Could have but not critical (Nice to have)
• W-Won't have this time, but potentially later

Online Agile tools

VersionOne
Atlassian