Only that node can talk to your backend right?
I'm using Keen UI @next a little. I had to hack it just a tad to propagate some click events but otherwise it was fine.
I could probably get behind what you're saying when I read definitions of "serverless architecture" like this: http://martinfowler.com/articles/serverless.html. Or when it's thrown around talking about containerization…
Dude. You're really focusing on the wrong thing here. No one is lying or attempting to deceive. At worst, the term is being used loosely - at worst. At best it's only referring to the portion of the work that happens…
It'd be cool if you knew what you were talking about. These definitely can be made to be serverless if you really needed to stick to that strict definition of the word. However, there is a small "introduction" broker…
Only that node can talk to your backend right?
I'm using Keen UI @next a little. I had to hack it just a tad to propagate some click events but otherwise it was fine.
I could probably get behind what you're saying when I read definitions of "serverless architecture" like this: http://martinfowler.com/articles/serverless.html. Or when it's thrown around talking about containerization…
Dude. You're really focusing on the wrong thing here. No one is lying or attempting to deceive. At worst, the term is being used loosely - at worst. At best it's only referring to the portion of the work that happens…
It'd be cool if you knew what you were talking about. These definitely can be made to be serverless if you really needed to stick to that strict definition of the word. However, there is a small "introduction" broker…