News for hackers. Stuff that matters.
Re:Systems Languages: An Experience Report by kbenson on Friday July 06, 2018 @03:10PM (#17474258)
Can I ask what you use as a database abstraction layer, if any, and what methods you use to convert your request params/JSON to queries?

I was playing around with trying to do this a while back (while also trying to learn Rust some), and it felt very cumbersome to have to write many specific Diesel update methods to handle different types of requests. It could have been my now knowing a better way to accomplish it, or it could have been the type of queries I was trying to model aren't a good fit for a staticly typed system like that (and there may be a better way to architect it). In any case, it felt like I was poorly approximating the strict typing I had already implemented in Postgres, a few times over, when I would be happy just handing it to Postgres and letting it throw out errors as needed.

Re:Systems Languages: An Experience Report by staticassertion on Friday July 06, 2018 @04:11PM (#17474735)
The only data stores I currently use are redis and dgraph. I write raw dgraph queries, though I have a small, highly focused library that I use to generate some of them.

As for redis, I use it as a dumb KV store, no need for an abstraction layer.

Re:Systems Languages: An Experience Report by lazharichir on Saturday July 07, 2018 @05:06AM (#17477753)
Dgraph is awesome but lacking some serious basic features such as backups and automatic file format update on new versions. I hate to export it all, update, re-import...

But love it, and love the team at Dgraph/Badger.

Re:Systems Languages: An Experience Report by staticassertion on Saturday July 07, 2018 @11:55AM (#17479039)
Yes, it's young and that shows in some places. But I think the team has done an excellent job and it happens to fit my use case very well.