This is just a marketing article from sliplane.io founder. Sort of feel sorry while reading it as it's simply one sided. Doesn't explain about challenges with managing servers at all. OS patches, maintaining high availability while scaling etc. There are major companies such as Netflix already using serverless for years. There are lots of white papers Ted talks about it as well.
Not every schmuck can set up a service application figure out Lambda commands to make these things work on an AWS Cloud Server. Let's be honest spinning up a docker container is about a hundred times easier. So SlipKid does have some points.
However, let's be realistic: if you can't run your program from the CLI with a cURL command, what are you really doing? Authorized Rest based API calls require stateful workflows so you need to bake these concepts into your design to keep your software app easy to integrate.
Fair enough, but why would he talk about managing OSes? His argument was against serverless technology, not cloud technology entirely. Towards the middle of the article he listed 3 different cloud container services. AWS ECS and EKS come to mind. Where I work, someone set us up with render.com, which allows for deploying containers. So there are already infrastructure platforms that allow for deploying containers, without having to manage patches.
This shameless plug aside, I'm more interested in whether or not the comparison is all that accurate. Also, I'm quite out of practice on this stuff, and trying to get back into it - but I thought there was some strong arguments for why stateless was a useful design pattern, and all I'm seeing is that the alternative allows for maintaining state. But is that a good thing? Does that make it better?
What’s wrong with telling about your product if it’s true and helpful?
I think lambda functions are good for very specific heavy calculations that fluctuate like repeatedly sudden peaks where you need to absorb all requests in a tiny squeezed fraction of a second. and cannot afford to loose anyone. Or yo I need extremely large RAM for short AI computation etc. But of course for most services the standard and simple monolith is perfect. Why even go serverless? If you can write your own server, do it. Don’t pay for any of those giant clouds. In fact I got curious about this sliplane service and clicked to read about it and I guess I’m not the audience for it as I didn’t understand at a glance what is it about exactly and I assume it is related to the article so I’ll be glad to get more details here. What’s the innovation? What does it solve?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is just a marketing article from sliplane.io founder.
Sort of feel sorry while reading it as it's simply one sided. Doesn't explain about challenges with managing servers at all. OS patches, maintaining high availability while scaling etc.
There are major companies such as Netflix already using serverless for years. There are lots of white papers Ted talks about it as well.
This article is just for marketing.
fair enough, this is more personal ranting than marketing tho haha. I wouldve written the same anonymously
Thanks! I won't waste my time reading it
Not every schmuck can set up a service application figure out Lambda commands to make these things work on an AWS Cloud Server. Let's be honest spinning up a docker container is about a hundred times easier. So SlipKid does have some points.
However, let's be realistic: if you can't run your program from the CLI with a cURL command, what are you really doing? Authorized Rest based API calls require stateful workflows so you need to bake these concepts into your design to keep your software app easy to integrate.
SlipKid is a good one
Fair enough, but why would he talk about managing OSes? His argument was against serverless technology, not cloud technology entirely. Towards the middle of the article he listed 3 different cloud container services. AWS ECS and EKS come to mind. Where I work, someone set us up with render.com, which allows for deploying containers. So there are already infrastructure platforms that allow for deploying containers, without having to manage patches.
This shameless plug aside, I'm more interested in whether or not the comparison is all that accurate. Also, I'm quite out of practice on this stuff, and trying to get back into it - but I thought there was some strong arguments for why stateless was a useful design pattern, and all I'm seeing is that the alternative allows for maintaining state. But is that a good thing? Does that make it better?
What’s wrong with telling about your product if it’s true and helpful?
I think lambda functions are good for very specific heavy calculations that fluctuate like repeatedly sudden peaks where you need to absorb all requests in a tiny squeezed fraction of a second. and cannot afford to loose anyone. Or yo I need extremely large RAM for short AI computation etc. But of course for most services the standard and simple monolith is perfect. Why even go serverless? If you can write your own server, do it. Don’t pay for any of those giant clouds. In fact I got curious about this sliplane service and clicked to read about it and I guess I’m not the audience for it as I didn’t understand at a glance what is it about exactly and I assume it is related to the article so I’ll be glad to get more details here. What’s the innovation? What does it solve?