While I've been pitching Docker to my boss every since cgroups were introduced (a long time before Docker), I still don't understand how I could use it in practice
I'm hoping I can skip Docker as much as possible altogether. Not that it isn't important but there's a lot of hype. We went from "maintain your own server" to push-to-deploy (AppEngine, Heroku, AWS Elastic Beanstalk) to installing sofware over and over inside containers, to me it feels like a step back in terms of abstraction.
We need to move forward again.
Docker and k8s can be building blocks for that "future" but the same way we don't need to re-code every abstracted layer our apps sit on everytime we code something, I think containers are .
I subscribe to this view for the next few years:
Simon Wardley #EEA
@swardley
X : What's going to happen in cloud in 2019? Me : Nothing special. 1) Enterprise data centres will continue to close. 2) Cloud will decentralise in terms of provision not power i.e. Amazon will "invade" more of those holdouts with AWS Outpost. 3) Serverless will rocket.
13:32 PM - 15 Dec 2018
64154
Serverless + edge computing is going to be that abstraction for most apps, and in some cases it already is.
We're just at the beginning, that's all. We tend to equate serverless to function as a service, but it's so much more. Google has been offering serverless computing since 2008 with AppEngine, Heroku since 2007.
People use higher level languages all the time because of how more productive they are, even at the expense of "speed". Such productivity comes from abstraction among other things.
Don't know how big your organization is but this is a good article about pros and cons of serverless for startups: The business case for serverless.
ps. serverless is hyped as well :D
Darren Shepherd
@ibuildthecloud
@rstephensme@monkchips oh man... "serverless" is just like "cloud" in the early days, impossible to determine proper uses or marketing BS. I'd say serverless is the answer to "you said containers would make things simple and it's still too damn hard." So whatever that answer is, that's serverless
21:24 PM - 14 Dec 2018
518
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.
While I've been pitching Docker to my boss every since cgroups were introduced (a long time before Docker), I still don't understand how I could use it in practice
I'm hoping I can skip Docker as much as possible altogether. Not that it isn't important but there's a lot of hype. We went from "maintain your own server" to push-to-deploy (AppEngine, Heroku, AWS Elastic Beanstalk) to installing sofware over and over inside containers, to me it feels like a step back in terms of abstraction.
We need to move forward again.
Docker and k8s can be building blocks for that "future" but the same way we don't need to re-code every abstracted layer our apps sit on everytime we code something, I think containers are .
I subscribe to this view for the next few years:
Serverless + edge computing is going to be that abstraction for most apps, and in some cases it already is.
We're just at the beginning, that's all. We tend to equate serverless to function as a service, but it's so much more. Google has been offering serverless computing since 2008 with AppEngine, Heroku since 2007.
People use higher level languages all the time because of how more productive they are, even at the expense of "speed". Such productivity comes from abstraction among other things.
Don't know how big your organization is but this is a good article about pros and cons of serverless for startups: The business case for serverless.
ps. serverless is hyped as well :D