21–30 of 70 posts
Lambda is great but it is not serverless, but more a PaaS for microservices. Which is a great direction to head, but not the correct vocabulary. "Serverless" can more accurately be said of the P2P/decentralized movement: - https://ipfs.io/ - http://gun.js.org/ - https://zeronet.io/ - https://webtorrent.io/ etc.
If I hear "serverless" one more time I swear I'm going to shiv a bi78ch.
If I hear "serverless" one more time I swear I'm going to shiv a bi78ch.
The serverless term will confuse non-technical people to think there's actually no server infrastructure or software needed.
How does it compare to Apex? Anybody with experience on both? https://github.com/apex/apex PS: Besides the fact APEX is only for AWS, however, APEX is very mature.
[1] - https://github.com/openwhisk/openwhisk
[2] - https://www.iron.io/platform/ironworker/
[3] - https://galacticfog.github.io/
[4] - https://github.com/fabric8io/funktion
(Edited for Formatting)
Clearly I'm being a smart ass, but pointing out that 'serverless' is an idiotic marketing term.
I think serverless is a very misleading name, because it does still need server infrastructure and server software. The serverless term will confuse non-technical people to think there's actually no server infrastructure or software needed.
Non-technical people may assume no server infrastructure. From the developer perspective -this is accurate-; the actual hardware is handled by someone else, there is no concept of it that the developer has to work around.
I'm not sure why you'd think someone would believe no software would be needed; even when servers are involved, there is software located elsewhere, on a mobile phone or a web browser or similar. No one is going to say "Oh, serverless? Then I don't need my software development team any more!"
So there's no servers, anywhere in this? You don't run it on a computer or anything? Clearly I'm being a smart ass, but pointing out that 'serverless' is an idiotic marketing term.