Standardizing Microservice Development
summary
Argues that small shared developer scripts eliminate duplicated build and CI configs by driving naming, tooling and deployment patterns; demonstrates one-step local deployment that checks credentials, spins a docker stack, starts a DB image and deploys the app, and shows reusable Gradle fragments and Gradle init scripts plus git submodules to publish scripts centrally. Claims the approach scales (variables otherwise appear in ~200 services), integrates with GitLab CI, is testable in pipelines, and reduces onboarding and maintenance pain.
AI-written summary · about
chapters (20)
- 0:00Intro
- 2:27Gains of Standardization
- 5:11Developer Scripts
- 5:57Deployment Script
- 10:47Cleaning Up Docker
- 13:56Principles
- 15:29Naming
- 21:21Script Publishing
- 22:06Other Options
- 23:25Repository Context
- 26:27Submodule benefits
- 26:51How reusable Gradle scripts work
- 28:15Building the build script
- 29:13Applying external cradle files
- 30:13Overwriting tasks
- 30:53Idea Code Style
- 31:10Idea Code Style Script
- 31:53CI Pipelines
- 36:20Dev Scripts
- 37:28Learnings
related talks
36mWild Microservices and Imaginary DevOps
27mMicroservices Are ‘Easy’, Dependencies Are Hard
19mScaling Microservices Development
37mKnee Deep in Microservices
28mContinuous Integration Testing: Fully Test your Microservices Application, Early and Often
01h 04mDeploying and Scaling Microservices
01h 02mDesigning Microservices
36mCultivating a Microservice Culture Via Tooling