Building Server Side API Architecture
summary
Progressive server-side API architecture recommends three concrete stages: start with a minimal controller+model to learn Go, move database code into a datastore package behind interfaces to achieve dependency inversion, then add a service/application layer mirroring DDD for complex logic. Uses standard library (net/http) and the testing package to validate design and enable fast refactors. Applied on a small team (three backend engineers migrating from PHP) and yields clearer boundaries, easier tests, and incremental adoption.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:23About me
- 0:46Why I need server-side architecture
- 1:13Reality of building architecture
- 2:18Approach to build architecture Go Skills/Knowledge
- 3:231st goal: Simple Model-Controller
- 3:482nd goal: Model-Controller + DIP
- 5:12Summary
related talks
21mBuilding APIs in Go The Stack Without a Framework
27mBuilding Great Web APIs
44mHow Do You Structure Your Go Apps?
23mLessons from Building an API Management Platform
37mModern HTTP Architecture
31mImplementing RESTful APIs
18mSoftware Architecture Building Better Applications with Architecture Best Practices
44mHow Do You Structure Your Go Apps?
