Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Releasing Serverless Framework V.1, and Fundraising

serverless.com

Post reply on HN
Print view View original

11–20 of 56 posts

Re: Releasing Serverless Framework V.1, and Fundraising

#11

Post by joeblau »

ac360 wrote: post #5
bjacobel wrote: post #3

Are there other examples of an open-source community project taking on several million dollars in venture capital funding? It seems a bit odd to me. I'm not sure I'm comfortable using a presumably open-source, free (beer and speech) tool knowing that the group behind it will have to find a way to monetize their users in order to justify the investment from VCs at some point down the road. Open-source developers shoul…

Lots. Docker, HashiCorp... It's the go-to-market strategy for lots of products now, especially developer tools.

Yeah, it seems like the strategy from the VC perspective it to eventually get the team acquihired by Amazon, Google, Microsoft, or Facebook.

Re: Releasing Serverless Framework V.1, and Fundraising

#12

Post by mxuribe »

dolzenko wrote: post #10

So it Server less Framework that seems to be considerably tied to AWS servers . EDIT. Only writing this because its in fact possible to imagine serverLESS framework these days (web workers, p2p etc), but this seems to be just about more volatile servers.

A small point, but they look to at least consider other non-AWS providers (e.g. Azure) per their note here: https://serverless.com/framework/docs/guide/installing-serve...

Re: Releasing Serverless Framework V.1, and Fundraising

#14

Post by ohstopitu »

matlock wrote: post #4
miguelrochefort wrote: post #2

This is definitely a step forward for software development. I'm interested to see what people build with it.

Thanks Miguel. We're going to release more about our plans for the next steps in the Framework soon. I'm currently writing those and will share with the community in the very near future (CTO of Serverless here)

Hi, I have been using sls since 0.5.6 and I love using it. It's a pleasure to work with, and the community on Gitter is generally eager to help.

That said, 1) What's the schedule on the documentation for best practices for SLS in production?

2) What's an example workflow ? (something involving multiple devs, testing, CI etc.)

3) And lastly, What's the timeline on adding support to Google Cloud Functions (in alpha) and Azure Functions?

Re: Releasing Serverless Framework V.1, and Fundraising

#16

Post by matlock »

ohstopitu wrote: post #14
matlock wrote: post #4

Earlier quoted context omitted.

Thanks Miguel. We're going to release more about our plans for the next steps in the Framework soon. I'm currently writing those and will share with the community in the very near future (CTO of Serverless here)

Hi, I have been using sls since 0.5.6 and I love using it. It's a pleasure to work with, and the community on Gitter is generally eager to help. That said, 1) What's the schedule on the documentation for best practices for SLS in production? 2) What's an example workflow ? (something involving multiple devs, testing, CI etc.) 3) And lastly, What's the timeline on adding support to Google Cloud Functions (in alpha) an…

> 1) What's the schedule on the documentation for best practices for SLS in production?

These are the goals for the next releases, giving you better tooling and best practices to go from a few services to many services.

>2) What's an example workflow ? (something involving multiple devs, testing, CI etc.)

Thats still relatively standard, with good testing, CI, CD , ... but we'll also add more blogposts and docs around that.

> And lastly, What's the timeline on adding support to Google Cloud Functions (in alpha) and Azure Functions?

Can't give an exact timeline, but we're working with both to be ready once GCF goes into production and working with Azure to get support into Serverless as well. Really also depends on talking to more users to understand how they want to use those providers.

Re: Releasing Serverless Framework V.1, and Fundraising

#17

Post by matlock »

bjacobel wrote: post #7
matlock wrote: post #6

Earlier quoted context omitted.

Thanks, appreciate the shoutout! There certainly are other open source tools like ansible, Chef, Puppet, Hashicorp, MongoDB (and many more) that have started out as an Open Source project and are still OSS champions. We have many plans for monetisation and are working closely with small to enterprise scale companies on building products and services around the Framework that help you once your infrastructure has reac…

To expand on my last point, how are you balancing the needs of an open-source community (steady, stable feature development, good communication/outreach/support, dedication to supporting existing products) with the needs imposed on Serverless by the VC funding model (acquiring new users quickly, launching new products you can monetize, getting hockey stick growth)?

The Serverless Framework is at the core of all our monetisation strategies, so we need the Framework to be spread to as many developers and into as many teams as possible and allow for way more complex infrastructure to be built. So by necessity we'll be pushing really hard on moving the framework forward.

I don't think the needs of an open source community stay in stark contrast to VC funding model, because without the Framework getting a lot of traction our other products aren't as interesting. So we'll be working on getting that traction. And we can't do this just by ourselves. We wouldn't be here without the Contributor community (literally because they implement so many features) so without good communication, outreach, support, ... we won't be able to grow fast enough.

I can only tell you that it is our true intention to push the framework forward very hard and build monetisation around it as much as we can to build this into a long term sustainable company. The more help and feedback we get to build the right commercial products and get great revenue (so we can give our Investors as well as our Team a return as well) the happier everyone is, including the community.

Re: Releasing Serverless Framework V.1, and Fundraising

#18

Post by SEJeff »

matlock wrote: post #6
bjacobel wrote: post #3

Are there other examples of an open-source community project taking on several million dollars in venture capital funding? It seems a bit odd to me. I'm not sure I'm comfortable using a presumably open-source, free (beer and speech) tool knowing that the group behind it will have to find a way to monetize their users in order to justify the investment from VCs at some point down the road. Open-source developers shoul…

Thanks, appreciate the shoutout! There certainly are other open source tools like ansible, Chef, Puppet, Hashicorp, MongoDB (and many more) that have started out as an Open Source project and are still OSS champions. We have many plans for monetisation and are working closely with small to enterprise scale companies on building products and services around the Framework that help you once your infrastructure has reac…

hashicorp is a company started my Mitchel Hashimoto. There is no open source tool named hashicorp. Do you perhaps mean vagrant?

Re: Releasing Serverless Framework V.1, and Fundraising

#19

Post by dfederschmidt »

dolzenko wrote: post #10

So it Server less Framework that seems to be considerably tied to AWS servers . EDIT. Only writing this because its in fact possible to imagine serverLESS framework these days (web workers, p2p etc), but this seems to be just about more volatile servers.

There are pull-requests open which enable the framework to be used with Azure or IBM BlueMix OpenWhisk

Re: Releasing Serverless Framework V.1, and Fundraising

#20

Post by cphoover »

I really love the new development being done to simplify cloud deployments of stateless horizontally scalable services.

Once Serverless supports other λaas offerings I think this will really take off.

In addition to the big boys (Amazon, IBM, Google, Microsoft), I'd love to see some alternative stable open source providers come about. Maybe something built on top of kubernetes or docker swarm.

Post reply on HN