1) The document discusses using a microservices architecture (SOA) for a 6 month MVP project in Brazil for taxation. 2) It advocates using lightweight frameworks like Play and CouchDB to allow for minimum viable architecture and design while still achieving decoupling and flexibility. 3) The services defined are NFe, Report, Company, and User with CouchDB used for document storage to allow for versioning of documents and designs for ease of upgrades and deployments.

1. AWS, Play! CouchDB: Scaling SOA in the cloud
Christophe Marchal | Software Architect

2. christophe.marchal@ilegra.com
@toff63
http://github.com/toff63
http://francesbagual.net
About me

3. www.ilegra.com

4. Project
● MVP for
● 6 months
● Brazilian taxation
● 5 Developers + 1 Product Owner

5. Requirements
● Cadastre
● NFe validation
● Taxation violation reports
● Fix prices simulator
● Quotation price simulator

6. Non Functional goals
SOA

7. SOA para um prototipo?!

8. When I say SOA people think: Framework

9. When I say SOA people think: Framework

10. When I say SOA people think: Highly Complex
System

11. When I say SOA people think 5 year project

12. However, SOA is about Principles

13. SOA

14. SOA is about decoupling

15. SOA is about SOC

16. SOA is about Flexibility

17. Strategic goal: get the MVP ready on time
➔ Minimum viable architecture
➔ Minimum viable design
➔ Only create tests that are relevant
➔ Remove any waste

18. Evolutionary refinement

19. Definition of services
Define the first services:
● NFe
● Report
● Company
● User

20. Choosing Play!
HTTP server
Lightweight
Stateless
Easy to learn
Functional
Easy to create
API
AsynC IO
REACTIVE

21. Play SubProject

22. Play HTTP client

23. Play HTTP client: Internal Calls

24. Service design
Contract
Presentation
Service Layer
Persistence Gateway
Contract / Trait
HTTP + HTML
● Simple design
● SOC
● Trait yet in place for future separation
● Lightweight

25. Monolithic deploy: pre containers solution
NFe
user Report
company
● 1 debian package
● Each module independant
● No current need to have deploy isolation
● No current need to separate by service
profile

26. AWS Deploy

27. 1 conf to rule them all with AWS private DNS
Application config:
● couchdb.internal
● redis.internal
DNS configuration
change in every
environment

28. What kind of NoSQL ?
● NFe is a document
● Huge amount of NFe to store

29. Why CouchDB?
● HTTP Interface
● Incremental map/reduce
● Polyglot Persistence ready
● Easy and simple to use

30. CouchDB: DB and Documents
http://mycouchdbserver:5984/pessoas http://mycouchdbserver:5984/pessoas/1

31. CouchDB: Design documents
http://mycouchdbserver:5984/pessoas/_design/list_v1

32. SOA with CouchDB
● Version your document
● Version you Design Document
● You can get backward compatibility in your database
● Ease database index migrations
● Let you do Canary Deploys
● Let you do Continuous Deployment with no downtime
HOW
BENEfits

33. AWS Deploy

34. ElasticSearch for filtering

35. ElasticSearch for filtering

36. Almost no db is shared between services
NFE Service Report Service
NFe

37. But a scalable solution would be ...

38. Summary
● SOA isn’t about project size
● SOA can be applied to any project
● Don’t rush to complexity
● Create proper abstractions to handle potentials future problems
● Version everything in your system
● Take advantage of the cloud

39. Christophe Marchal | Software Architect
Thanks for your Attention! Any question?