This document discusses the journey of a software architect and their company from monolithic architecture to microservices. It began with moving 4 platforms to use microservices two years ago with goals of smaller deployments and lower risk. They now have 80 deployable projects using microservices with 2-5 services each. Microservices are described as small, independent units that implement domain features and can be understood by a single developer. The document contrasts monoliths, which are large, complex codebases for an entire business, with microservices and discusses how the company transitioned from monoliths to using microservices architecture.

1. Our journey to micro
services
Where did we end up

2. Me
• Software architect
– Been working in the industry for the past 12y
– working for ebay the past 4 years
2

3. Microservices at ebay classified group dk
• We started 2 years ago with microservices
– 4 platforms
– We needed smaller deployment, lower risk
– All deployment/scripts handled by siteops
• Now we have
– 80 deployable projects managed in octopus
– with 2-5 microservices within each
3

4. Monolith vs microservice
• Monolith
– a term for a big system
– usually runs considerable amounts of our business
– battle tested
– big and ugly codebase
• Microservice
– Small independent deployable unit
– Implements a few features from a particular domain
– Understandable by a single developer
http://dev.otto.de/2015/09/30/on-monoliths-and-microservices/
4

5. Monolith vs microservice
• MonolithFirst
– you shouldn't start a new project with microservices,
– Source: http://martinfowler.com/bliki/MonolithFirst.html
• Don’t start with a monolith
– … when your goal is a microservices architecture
– Source: http://martinfowler.com/articles/dont-start-monolith.html
5

6. Monolith – The developer comfort zone
6
Public string buisnessLogic(input){
return ”Hello ” + input;
}
Deployment
Authentication
Authrization
Configurationmanagement
Caching Communication
Exception
management
Validation
Logging and
Instrumentation
Buildmanagement
Infrastructure

7. Monolith – Our platforms
7

8. Microservices – many monoliths?
8

9. Microservices – Where did we start
9
Shared Service

10. Owin to framework glue
Owin – Handling cross cutting concerns
OWIN
Middlewares
Authentication
Caching
Logging
Validation
Exception management
Instrumentation
ASP.NET MVC ASP.NET API Nancy ServiceStack
10
IIS / Selfhost
HttpRequest HttpResponse

11. Owin – doing conventions
• OWIN defines a standard interface between .NET web
servers and web applications.
• The goal of the OWIN interface is to decouple server and
application, encourage the development of simple modules
for .NET web development, and,
• by being an open standard, stimulate the open source
ecosystem of .NET web development tools.
• Source: owin.org
11

12. CODE!
Owin middleware components
12

13. Owin middleware
13
• Vanilla • Intermingled • Middleware, seperations of concerns

14. Microservices at ebay
• Octopus deploy
– Configuration management
– Deployment
• Build management
– Teamcity
• Infrastructure
– Operations is working on automation with puppet
14
Deployment
Configurationmanagement
Buildmanagement
Infrastructure