21–30 of 56 posts
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.
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…
hashicorp is a company started my Mitchel Hashimoto. There is no open source tool named hashicorp. Do you perhaps mean vagrant?
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.
'Serverless' as currently jargoned is used to connote that the developer does not have to think about servers (or VM's or containers) directly. The 'serverless' buzzword does not mean that there are not servers somewhere doing useful work.
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
Earlier quoted context omitted.
There are pull-requests open which enable the framework to be used with Azure or IBM BlueMix OpenWhisk
Hmm if I recall they had logos of azure, ibm whisk, and google cloud fns in their project. Seems those logos have recently been removed. Is this indicative of the future of this project, leaning towards AWS lock-in?
Not just because users want those, but for us its important to become more provider independent as we don't otherwise have a defensible product. So multi-provider is definitely coming and we're in constant contact with many providers.
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.
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.
We're actually talking to everyone you mentioned. I'd love to see some "on-premise" Serverless infrastructure as well, the biggest issue with that is still the event system as a Serverless infrastructure really mostly makes sense if you can do things like "when you upload something to this bucket run this function". This is hard to replicate in an on-premise system.
Edit: An example of the kind of thing I am concerned will happen[2]. Use the word "serverless" in a project? Get a take down notice.
[1]http://tmsearch.uspto.gov/bin/showfield?f=doc&state=4802:t7t...
[2]https://twitter.com/sindresorhus/status/776142274564616192
Earlier quoted context omitted.
We're actually talking to everyone you mentioned. I'd love to see some "on-premise" Serverless infrastructure as well, the biggest issue with that is still the event system as a Serverless infrastructure really mostly makes sense if you can do things like "when you upload something to this bucket run this function". This is hard to replicate in an on-premise system.
I don't get what's so difficult to do on-prem. Your target market on-prem all use Kafka as their event bus and either Mesos or Kubernetes as their execution fabric - what's so tricky about fitting into that?
You can of course do something like that yourself in your own infrastructure, but then every piece of software needs to support it somehow, you need to manage that event bus infrastructure and you most likely have to push those events in yourself.
And that kind of thing is already there, so the appeal that Serverless event driven systems in the cloud have (because the providers give you all of this out of the box) is much harder to achieve when you have to do that yourself.