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
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
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
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
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
Service-Oriented Architecture ‣ Not Component-Oriented Architecture ‣ Loosely Coupled Elements ‣ Updatable one service doesn’t require changing any other services.
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
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
Keep Code at a Similar Level ‣ Actually, we don’t but we can do it. ‣ Immutable Infrastructure (Infrastructure As Code) ‣ Tesing: Continuous Integration
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
Each Microservices Responsible For ‣ Payment Service ‣ Already Released ‣ Responsible for Payment at eureka ‣ Search Service ‣ Write Code with net/http ‣ Elasticsearch is
Each Microservices Responsible For ‣ Surveillance Service ‣ Word Filtering ‣ Monitoring User (like Spam) ‣ Analysis Service ‣ for eureka ‣ Algorithm, Mathematical Analysis, Machine Learning, …
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
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! :)