add monolith vs microservice to readme

Author: Mulkave

readme.md

@@ -9,6 +9,8 @@ are indeed the next progression when applications scale and reach that turning p
 using Lucid, the transition process will be logically simpler to think about and physically straight-forward to
 implement.
 
+To see how it compares to the monolithic application and when to use which, check [Monolith vs. Microservice](#monolith-vs-microservice)
+
 ## Installation
 To get rolling, you need to create a new project using Composer:
 ```
@@ -133,6 +135,39 @@ That's it! Now serve the application with `php artisan serve` and visit `http://
 
 ---
 
+## Monolith vs. Microservice
+In the monolith Lucid application we have multiple services (i.e. Api, Web) and these typically will exist in
+`src/Services/Api` and `src/Services/Web` respectively. With the microservice the `src` does not exist, since
+it is intended to be one service serving a single purpose, the `app` directory will do.
+It will hold the following directories:
+- **Data** For all your models, repositories and value objects.
+- **Domains** Holds the Domains and their Jobs.
+- **Features** The service's Features.
+
+### Directory Structure
+| Component | Monolith | Microservice |
+|---------|---------|--------------|
+|Job | src/Domains/[domain]/Jobs/[job] | app/Domains/[domain]/Jobs/[job] |
+| Feature | src/Services/[service]/Features/[feature] | app/Features/[feature] |
+| Service | src/Service/[service] | N/A (app) as equivalent |
+
+### Tests
+One other significant difference is in the location of tests:
+
+|Component|Monolith | Microservice |
+|---------|---------|--------------|
+|Job | src/Domains/[domain]/Tests/Jobs/[JobTest] | tests/Domains/[domain]/Jobs/[JobTest] |
+| Feature | src/Services/[service]/Tests/Features/[FeatureTest] | tests/Features/[Feature]Test.php |
+
+## How To Choose
+It is always [recommended](http://martinfowler.com/bliki/MonolithFirst.html) that you start with a monolith
+and work on it until it gets so big that it is crucial to be dissected into single-purpose services (microservices).
+It would be challenging to be able to figure out the different services your application would need moving forward.
+
+This project is also useful when you know for sure that your application will not have to deal with multiple Services but you would still like to use Lucid.
+
+---
+
 # Laravel PHP Framework
 
 [![Build Status](https://travis-ci.org/laravel/framework.svg)](https://travis-ci.org/laravel/framework)