Day 2 - A deeper dive into the Server side Architecture

Quick reminder : 
I need to do a simple and funcky interface to access a NoSQL database (CouchBase). This database contains some datas from a CRM Application. A Qualification team needs a easy way to deal with the content of this database.

 Server side Big Picture :
Today, as I sit down in front of my computer, I know what I am going to do. I have to take a look at the server side of my archecture. Yesterday, I dealt with the client side part.
Now, it's time to swith to the server side. Based on a Tomcat, I won't need the JEE full stack bacause I'm gonna use all the power of Spring instead. So Tomcat server is enough.


I want to test Spring 4, it has just been released, it's a good opportunity.
Even if graddle is getting more and more important in the java community I stick with Maven. I feel more confident with it, I think, it's a good choice.

A more detailed view :
I'm going to slice my application in 4 major parts :

• restful provider : it will expose the json message
• business : all my business rules are here
• dao : it deals with accessing Couchbase
• technical : logging, exception, ... all this kind of stuff

Each part is a maven module, I have also a parent POM to specifyé dependencies, variables, ...

And now ? :
I need a few things before coding, setting up my environement for exemple.


So tomorrow I will start to install all the products, my IDE, my github repository.
To train myself, I will do my application using Test Driven Design (TDD). It's gonna be a good practice.