Lever OS

Infrastructure

self-hosted serverless platform

SHOW HN2016

191points
61comments
#144of 2,264 in 2016
Top 7%of 2016 by points

How HN took it

CuriousMostly questions and neutral comments

1 positive, 11 neutral or asking, 1 mixed, 5 critical, out of 18 comments about the project. Thread score -0.11.

Idea: 0 for, 5 againstExecution: 1 for, 0 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Sticky resource routing useful for data sharding

    From 1 comment
    • Interesting bit from the FAQ: "We rely heavily on Docker and Docker Swarm for containers, orchestration and networking. Other pieces of tech we use are Consul for service…
      zbjornson on HN
  • Open source alternative reduces vendor lock-in

    From 1 comment
    • So... this is backend infrastructure (i.e. it runs on a server) to let your team deploy "severless" apps... So they're serverless. Except the server you're running it on. And the…
      stephenr on HN

Objections

  • Calling it serverless is misleading since servers still run

    From 2 comments
    • So... this is backend infrastructure (i.e. it runs on a server) to let your team deploy "severless" apps... So they're serverless. Except the server you're running it on. And the…
      stephenr on HN
    • > The serverless concept solves this problem, because it requires no DevOps to build and deploy applications at scale This is wonderfully naive. A great goal, but hopelessly…
      vidarh on HN
  • Ops concerns like logging and monitoring not addressed

    From 1 comment
    • > The serverless concept solves this problem, because it requires no DevOps to build and deploy applications at scale This is wonderfully naive. A great goal, but hopelessly…
      vidarh on HN
  • No data persistence yet

    From 1 comment
    • > The serverless concept solves this problem, because it requires no DevOps to build and deploy applications at scale This is wonderfully naive. A great goal, but hopelessly…
      vidarh on HN

Requests

  • Ability to provision instances automatically

    From 1 comment
    • Interesting bit from the FAQ: "We rely heavily on Docker and Docker Swarm for containers, orchestration and networking. Other pieces of tech we use are Consul for service…
      zbjornson on HN
  • Support for Python and Java

    From 1 comment
    • Your documentation says you support Node and Go. Do you have plans to support any other technologies?
      jackcosgrove on HN

Questions

  • How load balancing works without a central orchestrator

    From 1 comment
    • Interesting bit from the FAQ: "We rely heavily on Docker and Docker Swarm for containers, orchestration and networking. Other pieces of tech we use are Consul for service…
      zbjornson on HN
  • How it compares to AWS Lambda

    From 2 comments
    • I'm not sure I fully understand. Can you compare this to AWS Lambda?
      skrowl on HN
    • So how is this better than Lambda or Iron.io Push Queues?
      biznickman on HN

Alternatives named

  • Serverless Framework

    From 1 comment
    • It looks like Serverless? https://github.com/serverless/serverless
      Thaxll on HN
  • AWS Lambda

    From 2 comments
    • A big part of the value of AWS Lambda is that it allows you to glue together other AWS services with custom application logic, similar to stored procedures in a database. Without…
      csears on HN
    • I'm not sure I fully understand. Can you compare this to AWS Lambda?
      skrowl on HN
  • Zappa

    From 1 comment
    • This reminds me of Zappa [0], only Zappa actually runs on AWS Lambdas. Although they readily admit it takes a lot of hacks to get WSGI working within a Lambda function. 0:…
      kolanos on HN
  • Iron.io

    From 1 comment

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/11683121)