Example JSON API with proper separation of concerns. about go-in-5-minutes HOT 12 CLOSED

@gotjosh Do you mean mocking out an external JSON API in a program?

from go-in-5-minutes.

No, i meant, using Business Objects to build an API. As in UserCreator which could receive the DB context, and a reference to an user to save it.

from go-in-5-minutes.

@gotjosh let me think on this, there's a lot of potential content here

from go-in-5-minutes.

I'm not much of an expert on Go but if you'd like/need any help I'b be more than willing!

from go-in-5-minutes.

thanks a ton @gotjosh - I may take you up on that when I develop code & outline for this one.

from go-in-5-minutes.

👍

from go-in-5-minutes.

👍

from go-in-5-minutes.

@gotjosh @vdemario @carlisia wondering if #24 (https://www.youtube.com/watch?v=QvWUCYwmExE) covered some of the topics here? I'm looking for drill down to specifics in this screencast

from go-in-5-minutes.

@arschles I think so; it'll be good to see a deep dive on this for sure.

from go-in-5-minutes.

I think so too.

from go-in-5-minutes.

I'm gonna start developing content for this topic soon, and I'll be mentioning everyone here in the PR.

initial ideas for splitting this up, for my future reference:

1. mapping JSON request/response structs to data storage "objects" (likely structs)
2. dealing with a 'user' object or other authentication context when doing operations (probably some overlap with #15). includes translating some incoming token to a user (if OAuth, requires a DB operation)
3. separating, handlers ('business logic'), data object ('models') and database implementation (overlap with #43)

from go-in-5-minutes.

👏

from go-in-5-minutes.