Show HN: Serverless meets Microservices

191 点作者 vladaionescu大约 9 年前

15 条评论

vidarh大约 9 年前

> The serverless concept solves this problem, because it requires no DevOps to build and deploy applications at scaleThis is wonderfully naive. A great goal, but hopelessly unrealistic. E.g. currently it is not handling data persistence at all, so for starters it's targeting "the easy bit", yet there's hardly any mention of things like logging, or what do to when their Consul cluster decides to start complaining because membership has gotten messed up (ever had a Consul node rejecting most messages as "suspect"? ever had the same node get registered twice? all kinds of fun stuff), how to analyse performance issues, networking problems etc.It looks like an interesting platform, but anyone thinking this gets them out of understanding ops concerns will have tough times ahead..

评论 #11684085 未加载

zbjornson大约 9 年前

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 discovery and gRPC with Protobuf for the RPC."Awesome that it's using gRPC under the hood. But, I'm still missing if there's an orchestration service running somewhere that takes care of the load balancing, or if it's distributed?"When deploying Lever, you allocate a number of servers to it. Lever can then manage resources and auto-scale services running on it - but this is only limited to the servers you have allocated to it."It would be awesome (and critical to our use case) if it could provision instances, even if it's via a shell command manually entered into a config file. From the stack description quoted above, it sounds like it would do okay if it was coupled with an autoscaling group that does this function for now...Finally, I love the sticky resource routing, with the use case being data sharding.Excited to try this out.

评论 #11684371 未加载

fortytw2大约 9 年前

Isn't a core tenant of DevOps that your developers are the ones doing the Ops too? I keep hearing things like "Hiring DevOps" or "According to the Stack Overflow survey there is 1 DevOps for every 30 developers.", and that feels like... an Ops role, right?

评论 #11683416 未加载

评论 #11683851 未加载

评论 #11683712 未加载

评论 #11684158 未加载

评论 #11683388 未加载

评论 #11686980 未加载

评论 #11683349 未加载

eistrati大约 9 年前

This is really great initiative! Despite some fundamental critics and misconceptions, I'd like to say: Congrats, Vlad Alexandru!In my humble opinion, this is not even close to "serverless", but rather "cross-platforms". The best description to current "serverless trend" that I've heard is that "infrastructure comes with no-ops and pre-scaled at massive scale, that only providers like Amazon's AWS, or Google's GCP, or Microsoft's Azure and alike can provide" ;)

stephenr大约 9 年前

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 lamba/style code they wrote and uploaded to it.But serverless, because no ops staff required. Except the ones who installed and maintain this.This is like a snake eating its own tail and wondering what hurts.Edit: despite my sarcasm, it's always good to see open-source solutions to reduce reliance (or risk of reliance) on closed vendor solutions. Just stop calling it serverless, and I'll stop telling you how fucking ridiculous that name is.

评论 #11683975 未加载

评论 #11684833 未加载

评论 #11684349 未加载

评论 #11684292 未加载

toddnni大约 9 年前

Is this a community project or built by a startup? I didn't find the information.

评论 #11683511 未加载

评论 #11683431 未加载

siscia大约 9 年前

I was developing something similar with effe[1] e effe-tool[2], the idea is similar.You wrote your service in go following in such a way that it expose 3 function and it get compiled down to a single binary, then you can dockerize your application (images usually are smaller than 6MB) and deploy it, wherever and whenever you want.Of course everything is open source.I explained it a little better here: <a href="http://redbeardlab.tech/2016/03/05/effe.html" rel="nofollow">http://redbeardlab.tech/2016/03/05/effe.html</a>[1]: <a href="https://github.com/siscia/effe" rel="nofollow">https://github.com/siscia/effe</a>[2]: <a href="https://github.com/siscia/effe-tool" rel="nofollow">https://github.com/siscia/effe-tool</a>

jackcosgrove大约 9 年前

Your documentation says you support Node and Go. Do you have plans to support any other technologies?

评论 #11683791 未加载

marknadal大约 9 年前

I don't know why HN is being so critical, because this sounds awesome and really useful! Similar to what I've been trying to do with databases ( <a href="http://gun.js.org" rel="nofollow">http://gun.js.org</a> ).It is sad to see so much elitism in the tech world that is dismissive of anyone/anybody that knows less than them. This same attitude seems to come out a lot to dismiss really cool tools like this ( <a href="http://leveros.com" rel="nofollow">http://leveros.com</a> ) that help solve frustrations and problems. Could we try to be more encouraging of newcomers and of tools that automate (laziness is a programmer's virtue) those gaps?

评论 #11685950 未加载

Thaxll大约 9 年前

It looks like Serverless? <a href="https://github.com/serverless/serverless" rel="nofollow">https://github.com/serverless/serverless</a>

评论 #11683609 未加载

csears大约 9 年前

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 the other AWS services and the event triggers they expose to Lambda, "serverless" is a lot less interesting.

评论 #11686496 未加载

danielrhodes大约 9 年前

So I know something like this (or AWS Lambda) is good for quickly putting up an endpoint and scaling it to theoretically unlimited nodes.Could anybody shed some light on how this might be used in practice? It seems at the point that you have multiple endpoints, you may as well just deploy a full application.

kolanos大约 9 年前

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: <a href="https://github.com/Miserlou/Zappa" rel="nofollow">https://github.com/Miserlou/Zappa</a>

skrowl大约 9 年前

I'm not sure I fully understand. Can you compare this to AWS Lambda?

biznickman大约 9 年前

So how is this better than Lambda or Iron.io Push Queues?