In recent weeks, I have been reading and trying out the concepts of polyglot persistence. In my upcoming posts, I will write more about my experience in this area. Today, we will talk about a common question that arises for many developers – when do I write my Unit Tests? or Is Test Driven Development (TDD) right for me?
When you search for TDD online, you find many links “for” the paradigm, and some “against”. The primary reason given by the folks who are against TDD, state that if followed strictly, TDD goes against concepts of “good” software architecture, for the application you are trying to write. This is the same argument that is given against Agile development as well. The point made is, the developer is to “too focused” on what they are solving “right now”, and doesn’t keep into consideration the “big picture” Continue reading
In today’s post, we will talk about setting up the database. While most developers prefer to work in a Code-First kind of an approach, I will using a Database-First approach for this project. The main reasoning behind this is that in almost all real world examples, someone else will be creating the database (or already has), for your application. While Code-First allows integrating with an existing database, the actual database-first route makes more sense to me. Continue reading
As we move into the third part of our series, we will talk a little about what architecture are we catering to. As mentioned in the series title, we would like to design an N-tier service oriented application. Lets see what that means first: Continue reading
Welcome to the second part of this series. Today we will talk about setting up source control.
Why do we need source/version control?
I think I won’t add anything new to the conversation if I say the following are some of the nice features any version control offers:
- consistency of file and directory names among all team members
- easy to revert changes
- better team communication
- potentially easy deployment of code
- tracking what was changed and who made the change Continue reading
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). Continue reading