home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 645030262

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions issue performed_via_github_app
https://github.com/simonw/datasette/issues/850#issuecomment-645030262 https://api.github.com/repos/simonw/datasette/issues/850 645030262 MDEyOklzc3VlQ29tbWVudDY0NTAzMDI2Mg== 9599 2020-06-16T21:51:01Z 2020-06-16T21:51:39Z OWNER

File locking is interesting here. https://docs.aws.amazon.com/lambda/latest/dg/services-efs.html

Amazon EFS supports file locking to prevent corruption if multiple functions try to write to the same file system at the same time. Locking in Amazon EFS follows the NFS v4.1 protocol for advisory locking, and enables your applications to use both whole file and byte range locks.

SQLite can apparently work on NFS v4.1. I think I'd rather set things up so there's only ever one writer - so a Datasette instance could scale reads by running lots more lambda functions but only one function ever writes to a file at a time. Not sure if that's feasible with Lambda though - maybe by adding some additional shared state mechanism like Redis?

{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 1,
    "rocket": 0,
    "eyes": 0
}
639993467  
Powered by Datasette · Queries took 1.099ms · About: github-to-sqlite