Welcome to the first of (possibly) many posts about me setting up an N-tier service oriented application architecture. In this and the posts that follow, I will try to recount some obvious, and some not-so-obvious elements in setting up an application. Initially the application will have a responsive web client, but the architecture will be setup in a way so as to support other potential clients (mobile apps being the obvious one).
Lets start with the basics. Here are the high level technology elements that I will use in my experiments:
- ASP.NET MVC 4 (to be upgraded when needed)
- ASP.NET Web API
- C# as the language of choice
- Entity Framework
- MySQL 5.5x database server – Instead of using SQL Server express, I opt to use MySQL. The main rationale behind this to get a fully functional database with no restrictions, which can be used if I decide to “launch” the application. This helps me avoid major licensing fees to MS!
- MySQL Workbench for database modeling
- Visual Studio 2012
- Kendo UI (when I get to the web elements)
Looks like a good place to start. Be back in a few days for part 2!