Why is it easy for an android developer to build MicroServices (and why most of them don’t do it)
summary
Claim: Android experience maps to backend so developers reuse tools and patterns to ship microservices in weeks. Uses Kotlin + Gradle, Micronaut for cloud-native DI, coroutines, JUnit/Mockito tests and KTlint/detekt for static analysis. Translates Room/ORM work to Room → Hibernate entity/repository models, controllers replace viewmodels, and build output is effectively APK is a JAR deployable as a service. A small team builds, tests (≈80% coverage) and deploys a working SumUp microservice in about two to two and a half months.
AI-written summary · about
chapters (10)
- 0:00Introduction and motivation
- 4:40What are microservices
- 7:27Choosing the tech stack
- 9:13Clean architecture comparison
- 12:18Database and ORM similarities
- 14:25Unit testing parallels
- 15:48Static code analysis and tools
- 17:35Building and deploying services
- 18:59Code structure walkthrough
- 24:12Results and benefits
related talks
40mDeveloping Micro Services With Kotlin
34mPainless Microservices with Kotlin
58mModern Android Development
17mBest Practises for Android Development as a Daily Business
37mTackling Android Development at Scale
32mBuild a modular Android app architecture
54mXfinity Connected Living: building really, really big android apps
46mModern Android Development