It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
I think serverless (aka "someone else's server") isn't really a departure from the trend -- more cloud management, more automation, more build & deploy, less and less straightup administration. I don't see container orchestration going anywhere, I'm afraid ;)
I've seen a handful of compelling use cases for blockchain. One involved a distributed database of 3D models/CAD stuff where licensing, authorship, and versioning were all concerns. A peer-to-peer append-only ledger makes sense for something like that, but it's pretty specialized.
Yeah, my naive hope is that serverless would make container orchestration another "auto" layer. You (as in devops) would still need to know how to operate on that layer if needed but you wouldn't really need to write Dockerfile(s) or figure out a way to monitor containers at scale.
Regarding blockchain... I agree, they marketed it (to companies and even consumers) as the next revolution in tech WAY before they actually had something revolutionary to corroborate such statement.
And if you cry wolf too many times... :-D I am sure there are people out there tackling problems the blockchain would indeed solve, I'm not sure replacing PayPal is chief among those (except if greed is your compass because you're not actually solving the trust problem nor helping the user experience).
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.
I think serverless (aka "someone else's server") isn't really a departure from the trend -- more cloud management, more automation, more build & deploy, less and less straightup administration. I don't see container orchestration going anywhere, I'm afraid ;)
I've seen a handful of compelling use cases for blockchain. One involved a distributed database of 3D models/CAD stuff where licensing, authorship, and versioning were all concerns. A peer-to-peer append-only ledger makes sense for something like that, but it's pretty specialized.
Blockchain seems like an inherently specialized tool. The grand generalizations seem really steeped in a capitalist gold rush.
Yeah, my naive hope is that serverless would make container orchestration another "auto" layer. You (as in devops) would still need to know how to operate on that layer if needed but you wouldn't really need to write Dockerfile(s) or figure out a way to monitor containers at scale.
Regarding blockchain... I agree, they marketed it (to companies and even consumers) as the next revolution in tech WAY before they actually had something revolutionary to corroborate such statement.
And if you cry wolf too many times... :-D I am sure there are people out there tackling problems the blockchain would indeed solve, I'm not sure replacing PayPal is chief among those (except if greed is your compass because you're not actually solving the trust problem nor helping the user experience).