Routing in Go Part 3: The last upgrade
By now we have a small Go API that is not embarrassing. For the last part, we are going to add the stuff that turns “cute demo” into “this could actually run”
API Design
All writings tagged with "API Design"
By now we have a small Go API that is not embarrassing. For the last part, we are going to add the stuff that turns “cute demo” into “this could actually run”
In part 1 we built a small payment links API. In part 2 we are going to do the things everyone promises they will do “after launch” and then never do until something catches fire.
So in this note, we are going to build a Go server with routing that stays boring and predictable. Boring is good. Boring survives.
I wanted a sandbox. In other words i wanted continuity of identity and discontinuity of data. Production is where mistakes cost money. Sandbox is where mistakes cost pride.
An API is a promise to unknown consumers about how your system behaves. Once published, that promise is difficult to change without breaking trust.