~/talk

Building Server Side API Architecture

Talkat GopherCon 2019 · 2019-07-24..07-27· [api-design, software-architecture]
slides:none on file

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

  1. 0:00Start
  2. 0:23About me
  3. 0:46Why I need server-side architecture
  4. 1:13Reality of building architecture
  5. 2:18Approach to build architecture Go Skills/Knowledge
  6. 3:231st goal: Simple Model-Controller
  7. 3:482nd goal: Model-Controller + DIP
  8. 5:12Summary
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.