micro service architecture
DESCRIPTION
TRANSCRIPT
Service Architectureµ
Agenda
• Anatomy of a micro service• Micro service architecture by
example• The Good Parts of the solution• Tooling• Q&A
Anatomy of a micro service
Micro services are tiny apps talking via uniform interface
installed as well-behaved OS services.
java –jar micro-service.jar config.yml
Traditional application vs. µ service based
Micro service architecture by example
Dropwizard
• Jetty
• Jersey
• Jackson
• Metrics
• Guava
• Joda Time
• Hibernate Validator
• LiquiBase
• YAML configuration
• Graceful shutdown
• Command-line API
Foundation for production ready micro services developed by
Dropwizard on InfoQ goo.gl/2RYALb
Command-line API?
unrecognized argument '--tpye'Did you mean: --type
Internal Loan Underwriting System
Requirement №1
Perform underwriting according to rules
specified in DSL and store decisions in
relational DB.
“…according to rules specified in DSL
DSL hero is…
RDB hero is…
“…and store decisions in Relational DB
Underwriter
Relational DB
RESTful API / JSON
Internal Loan Underwriting System
Requirement №2
Fancy back-office application that allows users to
perform underwriting and look over decisions.
Why separate micro service?
• Back-office is a regular client. Many still to come.
• Back-office is stateful
• Back-office is server-centric, no JavaScript
experience
• Independent coding, testing & deployment
“…fancy back-office application
Fancy UI hero
is…
…because it’s Java conference
Underwriter
Relational DB
Back-Office
Internal Loan Underwriting System
Requirement №3
Collect credit history from various 3rd party
providers in parallel.
Why separate micro service?
• SRP!
• We have a team of Scala enthusiasts
• Operations must self-heal in case of failure –
Akka
• Independent coding, testing & deployment
Underwriter
Relational DB
Back-Office
Credit History Collector
Internal Loan Underwriting System
Requirement №4
Project codename «CHNAPI» - API for our brand new
partner «Chuck Norris».
Why separate micro service?
• Public service must run in DMZ
• Huge number of requests – queuing is a must
• Underwriter is not ready to scale – other dev
priorities
• We don’t know what kind of architecture to apply
yet
Underwriter & CHNAPI Gateway integration
• Push can cause overload• What if Underwriter is down?
Underwriter CHNAPIGateway?
HTTPUnderwriter CHNAPI
Gateway
• More elements in chain• How well does it scale?
JMSUnderwriter CHNAPIGateway
• CHNAPI exposes Feed• Underwriter polls CHNAPI
for updates
Underwriter CHNAPIGateway
HTTP Polling
Underwriter CHNAPIGateway
HTTP Polling
CHNAPIGateway
CHNAPIGateway
Load Balance
r
Load Balancer
DMZ
CHNAPI Gateway
JSON feed, OData or custom-crafted
Any JSON storage, e.g. MongoDB
CHNAPI Gateway
Underwriter
Relational DB
Back-Office
Credit History Collector
MongoDB
Internal Loan Underwriting System
Requirement №5
Chuck Norris is interested in all underwriting
decisions. Project codename «CHNORR».
Why separate micro service?
• Daily reporting, during active working hours
• External Client API with a tail of transitive
dependencies
• Neightbor dev team would like to use CHNORR!
Underwriter CHNORR
CHNORR
CHNORR
DMZ
CHNORR
Load Balancer
Events
Spring Batch
Any storage for keeping data in reporting-friendly format
HTTP
CHNAPI Gateway
Underwriter
Relational DB
Back-Office
Credit History Collector
MongoDB
CHNORR
MongoDB
The Good Parts of the solution
Toolset unchained
• Architectural approaches
• Polyglot• Storages
• Frameworks
Scalability
• HTTP stack• Independent
provisioning• Fine tuning
• Elasticity
Independence
• Development• Testing
• Deployment
How to deploy in a proper order?
Supply Dependency Descriptor
with each micro service. For example:
depend.yaml for foo-service
dependencies:group: com.microservicesartifact: bar-serviceversion: 2.x.x
-
How to deploy in a proper order?
We can forbid deployment in the wrong
order by validating dependencies on
Pipeline2.0.0
Test Prodbar-service
1.0.0
foo-service
Test Prod
1.9.0
bar-service
1.0.0
foo-service
How to develop?
Together with Dependency Descriptor
(DD), put Vagrant file with DD-fed
provisioner in a root source directory.
- depend.yaml
- Vagrantfileup
Launch app with test doubles in place of real dependencies
How to test?
For every dependency create a test
double
App
Foo
Bar Qux
Production
HTTP App
Foo-TD
Bar-TD
Testing
HTTP
Never mock internals. Mock externals
instead.
Tooling
Testing & Live Doc
• MOCO for test double creation
• REST-assured for testing REST APIs
• Cucumber for describing API usage with examples
• Relish for publishing Cucumbers online
A shipping container system for your apps
VM without an overhead of VM
Docker on InfoQ http://goo.gl/ALnjYt
Why Docker? Why Not Chef? goo.gl/iJ8Idl
Learn more • Micro Services by James Lewis goo.gl/PS7BYK
• Micro Services by Fred George goo.gl/dgd8Ya
http://goo.gl/khddl
Conclusion
The next morning, "we had this orgy of `one liners.' Everybody had a one liner. Look at this, look at that. ...Everybody started putting forth the UNIX philosophy. Write programs that do one thing and do it well. Write programs to work together. Write programs that handle text streams, because that is a universal interface." Those ideas which add up to the tool approach, were there in some unformed way before pipes, but they really came together afterwards. Pipes became the catalyst for this UNIX philosophy. "The tool thing has turned out to be actually successful. With pipes, many programs could work together, and they could work together at a distance."
The Unix Philosophy http://www.faqs.org/docs/artu/ch01s06.html
The next morning, "we had this orgy of `one liners.' Everybody had a one liner. Look at this, look at that. ...Everybody started putting forth the UNIX philosophy. Write programs that do one thing and do it well. Write programs to work together. Write programs that handle text streams, because that is a universal interface." Those ideas which add up to the tool approach, were there in some unformed way before pipes, but they really came together afterwards. Pipes became the catalyst for this UNIX philosophy. "The tool thing has turned out to be actually successful. With pipes, many programs could work together, and they could work together at a distance."
The next morning, "we had this orgy of `one liners.' Everybody had a one liner. Look at this, look at that. ...Everybody started putting forth the UNIX philosophy. Write programs that do one thing and do it well. Write programs to work together. Write programs that handle text streams, because that is a universal interface." Those ideas which add up to the tool approach, were there in some unformed way before pipes, but they really came together afterwards. Pipes became the catalyst for this UNIX philosophy. "The tool thing has turned out to be actually successful. With pipes, many programs could work together, and they could work together at a distance."
The next morning, "we had this orgy of `one liners.' Everybody had a one liner. Look at this, look at that. ...Everybody started putting forth the UNIX philosophy. Write programs that do one thing and do it well. Write programs to work together. Write programs that handle text streams, because that is a universal interface." Those ideas which add up to the tool approach, were there in some unformed way before pipes, but they really came together afterwards. Pipes became the catalyst for this UNIX philosophy. "The tool thing has turned out to be actually successful. With pipes, many programs could work together, and they could work together at a distance."
The next morning, "we had this orgy of `one liners.' Everybody had a one liner. Look at this, look at that. ...Everybody started putting forth the UNIX philosophy. Write programs that do one thing and do it well. Write programs to work together. Write programs that handle text streams, because that is a universal interface." Those ideas which add up to the tool approach, were there in some unformed way before pipes, but they really came together afterwards. Pipes became the catalyst for this UNIX philosophy. "The tool thing has turned out to be actually successful. With pipes, many programs could work together, and they could work together at a distance."
THANK YOU!