add database. create basic users table. allow some crud from UI to verify functionality.
what DB?!?!
i tried boltdb since the idea of a native go key/value store interested me, however I get the impression that we cannot scale the service this way, as only one process can have the DB opened at a time. so running 5 copies of the application, for example, would be impossible.
I liked the idea of trying key/value over relational, but realistically it probably makes more sense for relational since ultimately we'll have users with groups. This seems to fit pretty well with the idea of relational.
SO.. all that being said.. I think i'd like to start with sqlite with a plan to move to postgres later on. while getting started with less than a dozen users, sqlite should be more than enough.
I'm planning to NOT use any kind of ORM and just hand-craft the sql. I think this will help stay as close to pure golang as possible and give us the best experience in design patterns and whatnot....
trriplejay
commented
6 years ago
add database. create basic users table. allow some crud from UI to verify functionality.
what DB?!?!
i tried boltdb since the idea of a native go key/value store interested me, however I get the impression that we cannot scale the service this way, as only one process can have the DB opened at a time. so running 5 copies of the application, for example, would be impossible.
I liked the idea of trying key/value over relational, but realistically it probably makes more sense for relational since ultimately we'll have users with groups. This seems to fit pretty well with the idea of relational.
SO.. all that being said.. I think i'd like to start with sqlite with a plan to move to postgres later on. while getting started with less than a dozen users, sqlite should be more than enough.
I'm planning to NOT use any kind of ORM and just hand-craft the sql. I think this will help stay as close to pure golang as possible and give us the best experience in design patterns and whatnot....