4 ms·

Yeah, they said its "serverless" but it requires an AWS lambda function. I use Jekyll for my blog but I simply commit, push, and run a script that copies the fi

Yeah, they said its "serverless" but it requires an AWS lambda function. I use Jekyll for my blog but I simply commit, push, and run a script that copies the files to S3. https://www.tberra.com/aws/amazon/meta/2016/11/12/the-birth-of-a-blog/ https://www.tberra.com/aws/amazon/meta/2016/11/12/the-birth-... its not scheduled but I could easily tell linux to run that command once at whatever time I wanted.

g_delgado14 10y ago
AWS lambda functions __are__ serverless. There's no notion of uptime, provisioning or managing servers when using lambda.
- Lord_Zero 10y ago
  This is true, but what triggers the lambda function to run? Where does the lambda function run when its triggered?
  - climber604 10y ago
    Clearly you need to learn more about lambda https://aws.amazon.com/lambda/ https://aws.amazon.com/lambda/
  - davidwells 10y ago
    One lambda runs when github webhooks are fired: https://github.com/serverless/post-scheduler#github-webhook-architecture-overview https://github.com/serverless/post-scheduler#github-webhook-... The other lambda fires on a cron job https://github.com/serverless/post-scheduler#cron-job-architecture-overview https://github.com/serverless/post-scheduler#cron-job-archit...
  - derefr 10y ago
    "Serverless" really means "your code is run as a container with a finite lifetime on an arbitrary machine in a standardized, non-configurable PaaS machine cluster." In essence, it's a return to the "cgi-bin" model of scripting, where you write a script that only runs for the lifetime of one request, and then a web server will spin it up to respond to a relevant request and it'll terminate at the end of that request. The only differences in the modern instantiation of the concept, are that: 1. the "cgi-bin" directory is a mounted object store, common to an entire cluster; and 2. there's some fancy preloading logic that lets Lambda functions stay "hot" between calls to them, so that they can run very quickly. (Sort of like Phusion Passenger does for Ruby code, except with enough isolation to make it safe for multitenant environments. Heroku's old Alpine stack might be a better comparison.)
- chriswarbo 10y ago
  > There's no notion of uptime, provisioning or managing servers when using lambda. There's no notion of uptime, provisioning or managing Web sites when using Web sites; but the operators of the Web site certainly have to tackle such things. Likewise, I'm sure the operators of AWS lambda are very much concerned about such things, even if the users aren't. In that sense, wordpress.com is "serverless".
  - Spivak 10y ago
    This is really just a semantic argument. You're free to call it Function as a Service or FaaS if you want. Hosted WordPress is SaaS but not FaaS.
rhizome 10y ago
or add a cron job to `git mv` a file from `pending` to `current` and run the commit/publish cycle.

g_delgado14 10y ago

AWS lambda functions __are__ serverless. There's no notion of uptime, provisioning or managing servers when using lambda.

Lord_Zero 10y ago
This is true, but what triggers the lambda function to run? Where does the lambda function run when its triggered?
- climber604 10y ago
  Clearly you need to learn more about lambda https://aws.amazon.com/lambda/ https://aws.amazon.com/lambda/
- davidwells 10y ago
  One lambda runs when github webhooks are fired: https://github.com/serverless/post-scheduler#github-webhook-architecture-overview https://github.com/serverless/post-scheduler#github-webhook-... The other lambda fires on a cron job https://github.com/serverless/post-scheduler#cron-job-architecture-overview https://github.com/serverless/post-scheduler#cron-job-archit...
- derefr 10y ago
  "Serverless" really means "your code is run as a container with a finite lifetime on an arbitrary machine in a standardized, non-configurable PaaS machine cluster." In essence, it's a return to the "cgi-bin" model of scripting, where you write a script that only runs for the lifetime of one request, and then a web server will spin it up to respond to a relevant request and it'll terminate at the end of that request. The only differences in the modern instantiation of the concept, are that: 1. the "cgi-bin" directory is a mounted object store, common to an entire cluster; and 2. there's some fancy preloading logic that lets Lambda functions stay "hot" between calls to them, so that they can run very quickly. (Sort of like Phusion Passenger does for Ruby code, except with enough isolation to make it safe for multitenant environments. Heroku's old Alpine stack might be a better comparison.)
chriswarbo 10y ago
> There's no notion of uptime, provisioning or managing servers when using lambda. There's no notion of uptime, provisioning or managing Web sites when using Web sites; but the operators of the Web site certainly have to tackle such things. Likewise, I'm sure the operators of AWS lambda are very much concerned about such things, even if the users aren't. In that sense, wordpress.com is "serverless".
- Spivak 10y ago
  This is really just a semantic argument. You're free to call it Function as a Service or FaaS if you want. Hosted WordPress is SaaS but not FaaS.

rhizome 10y ago

or add a cron job to `git mv` a file from `pending` to `current` and run the commit/publish cycle.