Excellent, more competition in serverless means increased adoption. Even better if it is open source, in contrast to GOOG/AMZN/MSFT offerings! Seems like an undercutting attempt on the IBM side? Could someone with production-level serverless experience share his insights on OpenWhisk capabilities and roadmap? What's missing from the G/A/M stacks?
> Even better if it is open source, in contrast to GOOG/AMZN/MSFT offerings!
I have been interested in running a serverless setup for a while now, so I’ve been looking at different open source alternatives to AWS lambda. I considered OpenWhisk but felt IronFunctions would be quicker to setup and easier to run. Anyone has experience deploying/using both? Would anyone that is running OpenWhisk comment on the process to get it running?
You might be interested in [Oracle's] Fn Project, it is open source and created by the team behind IronFunctions. I think it started life as a fork of IronFunctions. It is written in Go. http://fnproject.io/
Thank you, will check it out. It did not come up during my (rather quick) search for alternatives.
I have been interested in running a serverless setup for a while now, so I’ve been looking at different open source alternatives to AWS lambda. I considered OpenWhisk but felt IronFunctions would be quicker to setup and easier to run. Anyone has experience deploying/using both? Would anyone that is running OpenWhisk comment on the process to get it running?
OpenWhisk can be started using Docker Compose locally with a single command (make quickstart) using this repo: https://github.com/apache/incubator-openwhisk-devtools/tree/... It can also be deployed on k8s with minimal effort: https://github.com/apache/incubator-openwhisk-deploy-kube There's also instructions for using VMs as the infrastructure layer: https://github.com/apache/incubator-openwhisk#quick-start If you h…
In my previous quick search I did not find the incubator-openwhisk-devtools repo, that left me with the impression that I had to run k8s which for my purposes is too heavy handed. A docker setup is more in line with my needs (run on vpc for quick side projects). thank you!
I have been interested in running a serverless setup for a while now, so I’ve been looking at different open source alternatives to AWS lambda. I considered OpenWhisk but felt IronFunctions would be quicker to setup and easier to run. Anyone has experience deploying/using both? Would anyone that is running OpenWhisk comment on the process to get it running?
OpenWhisk can be started using Docker Compose locally with a single command (make quickstart) using this repo: https://github.com/apache/incubator-openwhisk-devtools/tree/... It can also be deployed on k8s with minimal effort: https://github.com/apache/incubator-openwhisk-deploy-kube There's also instructions for using VMs as the infrastructure layer: https://github.com/apache/incubator-openwhisk#quick-start If you h…
It would be great if they explained that anywhere in their documentation.
Nowadays when someone claims to be "serverless", there can be two interpretations: 1. It's a server actually. It's just that the server serves up functions, without state. So a more correct terminology would be "stateless servers" 2. Truly P2P (Like blockchain), therefore there truly are no "servers". Used to think Amazon did a great job coming up with the jargon that's great for marketing, but lately as we see more…
They actually mean this - https://en.wikipedia.org/wiki/Common_Gateway_Interface . 1993 is the new 2018. edit: And the life of the Apache Web Server (the first AWS) started with that interface.
I was just telling my wife this morning that this "Serverless" business was just CGI reinvented. I don't get it.
Nowadays when someone claims to be "serverless", there can be two interpretations: 1. It's a server actually. It's just that the server serves up functions, without state. So a more correct terminology would be "stateless servers" 2. Truly P2P (Like blockchain), therefore there truly are no "servers". Used to think Amazon did a great job coming up with the jargon that's great for marketing, but lately as we see more…
They actually mean this - https://en.wikipedia.org/wiki/Common_Gateway_Interface . 1993 is the new 2018. edit: And the life of the Apache Web Server (the first AWS) started with that interface.
Clearly the next big development in this space will be some form of server-side scripting language which can be embedded in HTML and is tightly coupled with the web server, some sort of Hypertext Preprocessor.
I bet if AWS acquired ColdFusion from Adobe and rebranded it Elastic Markup Platform it'd be the hot new thing
They actually mean this - https://en.wikipedia.org/wiki/Common_Gateway_Interface . 1993 is the new 2018. edit: And the life of the Apache Web Server (the first AWS) started with that interface.
I was just telling my wife this morning that this "Serverless" business was just CGI reinvented. I don't get it.
I remember CGI; curious if you're able to elaborate how you see the analogy.
Was it ever a bad idea, or did it just go out of fashion? I'm not a PHP fan, but I miss the simplicity of low-end deployments on a LAMP stack by literally dragging files over FTP. It seems like something has been lost with the total embrace of more modern web frameworks.
It's just a difference in scale. I mean, you can still setup a FTP and drag and drop your files to deploy, if you want to. But companies with many developers deploying multiple changes per day, needs something that works better and faster. Not saying that serverless is for them, but that's why things get more complex sometimes. But you're still able to choose "older" things.
Definitely, I guess I just miss having a platform (LAMP) that scaled down as well as up. I think it's really cool that some of the most trafficked websites run WordPress and MediaWiki which can also be installed in a few clicks on a $5/month shared host. I recently wrote a Python web app that uses Dynamodb and Lambda and even though it's open source it feels way less portable.