6 ms·

You basically have a git repo that contains your business logic implemented as 'functions' and some configuration : knative will build, containerize, deploy, an

by gdsdfe 8y ago

You basically have a git repo that contains your business logic implemented as 'functions' and some configuration : knative will build, containerize, deploy, and glue/route those functions for you to make it a full fledged app. it will also take care of load balancing/scaling etc. So all you need really is focus on you business logic code and write some config for knative ... well this is at least the vision

djhworld 8y ago
Why isn't a polished version of this the blurb?
- gdsdfe 8y ago
  They need to hire me :)
  - dewitt 8y ago
    Email me. : ) We're hiring. I'm dewitt@ all the obvious places.
hn_throwaway_99 8y ago
How would this compare to something like serverless.com?
- gdsdfe 8y ago
  not sure they seem quite similar (I am not familiar with neither to be honest) but the main difference in my opinion is this is built on open source and backed by the big boys : google, IBM, SAP ..etc
- markusthoemmes 8y ago
  The serverless.com framework is built around existing serverless/faas platforms and allows you to write vendor-agnostic functions and deploy them exchangeably. It does not provide the resources to run your code. it abstracts away different API of different vendors to make them seem as one. Knative on the other hand provides building blocks to eventually build a serverless platform. It provides the resources necessary to run and scale your application. In short: You could use the serverless.com framework to deploy applications/functions on knative. But you still need some layer actually running your workload, like knative.
peterwwillis 8y ago
This is just a summary of what it is. A car is a machine that moves you around the roads. But how does the car work ? Are you using it? Because the docs seem to show that what you describe is not the case. The devs seem to have to write integrations for everything, so almost nothing is done for them. Saying Knative will "do it for you" is like saying your car will "drive itself". You only have to steer it and work the pedals ...
- gdsdfe 8y ago
  I am giving you the higher level view on what I think it does ... read the docs! or even better the source code it is open. Explaining to you how the car works can be as far as explaining how physics work, because you need understand combustion, gravity etc. EDIT: and that will exceed 20 sentences by a few very heavy books.
  - peterwwillis 8y ago
    According to the docs, the high level overview is misleading. You don't have to explain physics to explain how a car works. You only have to explain it in terms of something your audience is familiar with. Magnetization would be hard to explain to someone without physics, because there's no other parallel to quantum mechanics for the average person. But a car is based on general principles which most of us understand at a simplistic level. We understand "stickiness", so "stickiness" can stand in for "coefficient of friction". We understand "weight", so we don't have to explain how gravity works. We understand that fuel, oxygen and a spark creates a fire (or explosion), so we don't have to explain chemical reactions. We also understand that explosions exert a force on things around them. So when I say that an explosion in your car's engine exerts a force pushing against a piston, and that piston is connected to a rod, and that rod pushes on and turns a crank, which (skipping the transmission for brevity) turns an axle, which is connected to a wheel whose tire is stuck to the road, and that the weight of the car on the wheel forces either the road or the tire to move, we understand that even though the car is heavy and the turning force on the tire is pretty strong, the road is probably stronger and isn't going to move, so instead the tire moves, and the car is attached to the tire. So you can understand at a basic level how a car works without having to know physics. What I was asking for was what combination of components in what order are required to make the thing run, and how these things are accomplished without the developer seeming to have to do anything. If they've built a car for developers, that's great, but it seems more like they've created nuts and bolts.
sequoia 8y ago
So it's like Serverless framework for k8s? https://serverless.com/ https://serverless.com/
- gdsdfe 8y ago
  I think it's more like what you would use to build serverless.com a more fair comparison IMO would be to https://cloud.google.com/functions/ https://cloud.google.com/functions/ but it didn't use neither so ...
  - sequoia 8y ago
    serverless is a config/deploy thing that deploys "functions" (to lambda etc.), ties them to HTTP routes or other events, provisions resources (storage etc.), ties them to your applicatoins etc.. The main thing it does not do is scaling etc. because you're deploying to a platform that handles that.

by gdsdfe 8y ago

djhworld 8y ago

Why isn't a polished version of this the blurb?

gdsdfe 8y ago
They need to hire me :)
- dewitt 8y ago
  Email me. : ) We're hiring. I'm dewitt@ all the obvious places.

hn_throwaway_99 8y ago

How would this compare to something like serverless.com?

gdsdfe 8y ago
not sure they seem quite similar (I am not familiar with neither to be honest) but the main difference in my opinion is this is built on open source and backed by the big boys : google, IBM, SAP ..etc
markusthoemmes 8y ago
The serverless.com framework is built around existing serverless/faas platforms and allows you to write vendor-agnostic functions and deploy them exchangeably. It does not provide the resources to run your code. it abstracts away different API of different vendors to make them seem as one. Knative on the other hand provides building blocks to eventually build a serverless platform. It provides the resources necessary to run and scale your application. In short: You could use the serverless.com framework to deploy applications/functions on knative. But you still need some layer actually running your workload, like knative.

peterwwillis 8y ago

This is just a summary of what it is. A car is a machine that moves you around the roads. But how does the car work ? Are you using it? Because the docs seem to show that what you describe is not the case. The devs seem to have to write integrations for everything, so almost nothing is done for them. Saying Knative will "do it for you" is like saying your car will "drive itself". You only have to steer it and work the pedals ...

gdsdfe 8y ago
I am giving you the higher level view on what I think it does ... read the docs! or even better the source code it is open. Explaining to you how the car works can be as far as explaining how physics work, because you need understand combustion, gravity etc. EDIT: and that will exceed 20 sentences by a few very heavy books.
- peterwwillis 8y ago
  According to the docs, the high level overview is misleading. You don't have to explain physics to explain how a car works. You only have to explain it in terms of something your audience is familiar with. Magnetization would be hard to explain to someone without physics, because there's no other parallel to quantum mechanics for the average person. But a car is based on general principles which most of us understand at a simplistic level. We understand "stickiness", so "stickiness" can stand in for "coefficient of friction". We understand "weight", so we don't have to explain how gravity works. We understand that fuel, oxygen and a spark creates a fire (or explosion), so we don't have to explain chemical reactions. We also understand that explosions exert a force on things around them. So when I say that an explosion in your car's engine exerts a force pushing against a piston, and that piston is connected to a rod, and that rod pushes on and turns a crank, which (skipping the transmission for brevity) turns an axle, which is connected to a wheel whose tire is stuck to the road, and that the weight of the car on the wheel forces either the road or the tire to move, we understand that even though the car is heavy and the turning force on the tire is pretty strong, the road is probably stronger and isn't going to move, so instead the tire moves, and the car is attached to the tire. So you can understand at a basic level how a car works without having to know physics. What I was asking for was what combination of components in what order are required to make the thing run, and how these things are accomplished without the developer seeming to have to do anything. If they've built a car for developers, that's great, but it seems more like they've created nuts and bolts.

sequoia 8y ago

So it's like Serverless framework for k8s? https://serverless.com/ https://serverless.com/

gdsdfe 8y ago
I think it's more like what you would use to build serverless.com a more fair comparison IMO would be to https://cloud.google.com/functions/ https://cloud.google.com/functions/ but it didn't use neither so ...
- sequoia 8y ago
  serverless is a config/deploy thing that deploys "functions" (to lambda etc.), ties them to HTTP routes or other events, provisions resources (storage etc.), ties them to your applicatoins etc.. The main thing it does not do is scaling etc. because you're deploying to a platform that handles that.