eureka Go ~Our Designing of a Microservices Architecture~

- Microservices at eureka
-- Design a Microservices Architecture
-- The Microservices Architecture of pairs
- Project Structure
-- Build up the pairs Project
-- Development Operations
- Web Application Framework

Transcript

1. eureka Go @kaneshin
2. Shintaro Kaneko (kaneshin) - Photographer and Engineering Manager at eureka, Inc. kaneshin kaneshinth shintaro.kaneko Mathematics: Optimization Problems 2010 2012 2011 Quality Assurance Engineer at eureka Real Estate in Vancouver, Canada
3. Agenda ‣ Microservices at eureka ‣ Design a Microservices Architecture ‣ The Microservices Architecture of pairs ‣ Project Structure ‣ Build up the pairs Project ‣ Development Operations ‣ Web Application Framework
4. Microservices at eureka
5. BEFORE THAT :)
6. The Monolithic Architecture of pairs (PHP)
8. ʊਓਓਓਓਓਓʊ ʼɹMonolithɹʻ ʉ̮̮̮̮̮̮ʉ
9. Monolith?
10. Our Designing of a Microservices Architecture
11. Our Designing of a Microservices Architecture ‣ Service-Oriented Architecture ‣ Separated Data Store from a Specific Layer ‣ Keep Code at a Similar Level ‣ Do a Separate Build for Each Microservice
12. Our Designing of a Microservices Architecture ‣ Service-Oriented Architecture ‣ Separated Data Store from a Specific Layer ‣ Keep Code at a Similar Level ‣ Do a Separate Build for Each Microservice
13. Service-Oriented Architecture ‣ Not Component-Oriented Architecture ‣ Loosely Coupled Elements ‣ Updatable one service doesn’t require changing any other services.
14. Our Designing of a Microservices Architecture ‣ Service-Oriented Architecture ‣ Separated Data Store from a Specific Layer ‣ Keep Code at a Similar Level ‣ Do a Separate Build for Each Microservice
15. Separated Data Store from a Specific Layer
16. Separated Data Store from a Specific Layer
17. Our Designing of a Microservices Architecture ‣ Service-Oriented Architecture ‣ Separated Data Store from a Specific Layer ‣ Keep Code at a Similar Level ‣ Do a Separate Build for Each Microservice
18. Keep Code at a Similar Level ‣ Actually, we don’t but we can do it. ‣ Immutable Infrastructure (Infrastructure As Code) ‣ Tesing: Continuous Integration
19. Our Designing of a Microservices Architecture ‣ Service-Oriented Architecture ‣ Separated Data Store from a Specific Layer ‣ Keep Code at a Similar Level ‣ Do a Separate Build for Each Microservice
20. The Microservices Architecture of pairs (Up to now)
22. The Microservices Architecture of pairs (From now on)
23. ɾ ɾ ɾ
24. Batch Batch Batch ɾ ɾ ɾ
25. Batch Batch Batch ɾ ɾ ɾ Service-Oriented Architecture Separated Data Store Separate Build
26. Each Microservices Responsible For ‣ Payment Service ‣ Already Released ‣ Responsible for Payment at eureka ‣ Search Service ‣ Write Code with net/http ‣ Elasticsearch is
27. Each Microservices Responsible For ‣ Surveillance Service ‣ Word Filtering ‣ Monitoring User (like Spam) ‣ Analysis Service ‣ for eureka ‣ Algorithm, Mathematical Analysis, Machine Learning, …
28. Each Microservices Responsible For ‣ And More ‣ Auth ‣ Like ‣ Message ‣ …
29. Project Structure
30. How to Build up the Project?
31. Server-Side Specifications ‣ Internationalization (i18n) ‣ Web Application Framework ‣ Revel, Goji ‣ Testing Tools ‣ onsi/ginkgo, stretchr/testify/assert ‣ DB Management Tools ‣ xorm (ORM), goose (Migration) I’m not going to talk about tools today.
32. Repository Structure
33. Early Period
34. pairs-admin.git pairs-web.git
35. Simple!
36. Middle Period
37. pairs-admin.git pairs-web.git pairs-core.git
38. Then
39. payement.git pairs-core.git pairs-search.git pairs-batch.git pairs-admin.git pairs-web.git
40. Pretty Good?
43. Complex and Risky
44. Integrated Repository
45. payement.git pairs.git
46. Integrated Repository ‣ Maintenance of Git Respository ‣ Didn’t Purge All Commits (logs) ‣ Throw away useless files (garbage) ‣ Problems of Continuous Integration ‣ All components to run tests
47. Development Operations
49. push webhook webhook
50. push webhook - Verify Code (Static Analysis) - Documentation - JSON Hyper Schema (HTML) - Database Schema (HTML) webhook
51. push webhook - Verify Code (Static Analysis) - Documentation - JSON Hyper Schema (HTML) - Database Schema (HTML) push webhook
52. Web Application Framework
53. Web Application Framework at eureka ‣ Revel (pairs) ‣ goji (payment, reception) ‣ gin (xxxxxxx)
54. I prefer to use net/http
55. So
56. Good bey Revel from pairs! (forever)
57. Why?
58. …
59. Agenda ‣ Microservices at eureka ‣ Design a Microservices Architecture ‣ The Microservices Architecture of pairs ‣ Project Structure ‣ Build up the pairs Project ‣ Development Operations ‣ Web Application Framework Talk to me after that! :)
60. Copyright © 2009-2015 eureka, Inc. All rights reserved. Thank you