▲ 27 ▼ All you need is PostgreSQL (ebellani.github.io) submitted 3 months ago by yogthos@lemmy.ml to c/programming@lemmy.ml 9 comments fedilink hide all child comments
[–] davel@lemmy.ml 8 points 3 months ago (6 children) *Except when all you need is SQLite. permalink fedilink source hideshow 6 child comments replies: [–] yogthos@lemmy.ml [S] 5 points 3 months ago (5 children) Yeah, it's amazing how good SQLite is nowadays. I find I use it for a lot of local apps I make for myself cause it's just good enough. permalink fedilink source parent hideshow 5 child comments replies: [–] dessalines@lemmy.ml 2 points 3 months ago (4 children) SQLite is pretty incredible. I think it currently has even faster read performance than postgres. The only reason to not use it, is if you have a write-heavy DB, or you need some of postgres's extra features. permalink fedilink source parent hideshow 4 child comments replies: [–] Count042@lemmy.ml 3 points 3 months ago Or if you want too host it on NFS backed storage permalink fedilink source parent [–] yogthos@lemmy.ml [S] 3 points 3 months ago there have been some really neat projects using it too like this one https://github.com/biokoda/actordb permalink fedilink source parent [–] SocialistVibes01@lemmy.ml 3 points 3 months ago That's my take as well, PostgreSQL is amazing, but in simpler DB schemes SQLite is undefeatable. permalink fedilink source parent [–] gruf@lemmy.ml 3 points 3 months ago* we have more performance issues developing gotosocial with postgres than with sqlite. if we supported multinode deployments or horizontal scaling such that sqlite's concurrency got harder to reason-about I'm sure postgres would shine, but for a single process sqlite has been generally much faster and it hasn't required anywhere near as much prompting to get the query planner to behave as required. i also think when people assume sqlite is better for simpler applications, they think smaller. but no, for the same 25+GB databases sqlite has mopped the floor with performance. single-process multi-threaded sqlite is fantastic. permalink fedilink source parent
[–] yogthos@lemmy.ml [S] 5 points 3 months ago (5 children) Yeah, it's amazing how good SQLite is nowadays. I find I use it for a lot of local apps I make for myself cause it's just good enough. permalink fedilink source parent hideshow 5 child comments replies: [–] dessalines@lemmy.ml 2 points 3 months ago (4 children) SQLite is pretty incredible. I think it currently has even faster read performance than postgres. The only reason to not use it, is if you have a write-heavy DB, or you need some of postgres's extra features. permalink fedilink source parent hideshow 4 child comments replies: [–] Count042@lemmy.ml 3 points 3 months ago Or if you want too host it on NFS backed storage permalink fedilink source parent [–] yogthos@lemmy.ml [S] 3 points 3 months ago there have been some really neat projects using it too like this one https://github.com/biokoda/actordb permalink fedilink source parent [–] SocialistVibes01@lemmy.ml 3 points 3 months ago That's my take as well, PostgreSQL is amazing, but in simpler DB schemes SQLite is undefeatable. permalink fedilink source parent [–] gruf@lemmy.ml 3 points 3 months ago* we have more performance issues developing gotosocial with postgres than with sqlite. if we supported multinode deployments or horizontal scaling such that sqlite's concurrency got harder to reason-about I'm sure postgres would shine, but for a single process sqlite has been generally much faster and it hasn't required anywhere near as much prompting to get the query planner to behave as required. i also think when people assume sqlite is better for simpler applications, they think smaller. but no, for the same 25+GB databases sqlite has mopped the floor with performance. single-process multi-threaded sqlite is fantastic. permalink fedilink source parent
[–] dessalines@lemmy.ml 2 points 3 months ago (4 children) SQLite is pretty incredible. I think it currently has even faster read performance than postgres. The only reason to not use it, is if you have a write-heavy DB, or you need some of postgres's extra features. permalink fedilink source parent hideshow 4 child comments replies: [–] Count042@lemmy.ml 3 points 3 months ago Or if you want too host it on NFS backed storage permalink fedilink source parent [–] yogthos@lemmy.ml [S] 3 points 3 months ago there have been some really neat projects using it too like this one https://github.com/biokoda/actordb permalink fedilink source parent [–] SocialistVibes01@lemmy.ml 3 points 3 months ago That's my take as well, PostgreSQL is amazing, but in simpler DB schemes SQLite is undefeatable. permalink fedilink source parent [–] gruf@lemmy.ml 3 points 3 months ago* we have more performance issues developing gotosocial with postgres than with sqlite. if we supported multinode deployments or horizontal scaling such that sqlite's concurrency got harder to reason-about I'm sure postgres would shine, but for a single process sqlite has been generally much faster and it hasn't required anywhere near as much prompting to get the query planner to behave as required. i also think when people assume sqlite is better for simpler applications, they think smaller. but no, for the same 25+GB databases sqlite has mopped the floor with performance. single-process multi-threaded sqlite is fantastic. permalink fedilink source parent
[–] Count042@lemmy.ml 3 points 3 months ago Or if you want too host it on NFS backed storage permalink fedilink source parent
[–] yogthos@lemmy.ml [S] 3 points 3 months ago there have been some really neat projects using it too like this one https://github.com/biokoda/actordb permalink fedilink source parent
[–] SocialistVibes01@lemmy.ml 3 points 3 months ago That's my take as well, PostgreSQL is amazing, but in simpler DB schemes SQLite is undefeatable. permalink fedilink source parent
[–] gruf@lemmy.ml 3 points 3 months ago* we have more performance issues developing gotosocial with postgres than with sqlite. if we supported multinode deployments or horizontal scaling such that sqlite's concurrency got harder to reason-about I'm sure postgres would shine, but for a single process sqlite has been generally much faster and it hasn't required anywhere near as much prompting to get the query planner to behave as required. i also think when people assume sqlite is better for simpler applications, they think smaller. but no, for the same 25+GB databases sqlite has mopped the floor with performance. single-process multi-threaded sqlite is fantastic. permalink fedilink source parent