请选择 进入手机版 | 继续访问电脑版

技术控

    今日:29| 主题:54680
收藏本版 (1)
最新软件应用技术尽在掌握

[其他] The Emergence Of Distributed POSIX

[复制链接]
檐铃伴风夜成眠 发表于 2016-11-27 15:07:01
172 3

立即注册CoLaBug.com会员,免费获得投稿人的专业资料,享用更多功能,玩转个人品牌!

您需要 登录 才可以下载或查看,没有帐号?立即注册

x
In the past couple of months I’ve noticed folks hinting at or suggesting something that, for a lack of a better term, I’ll call    distributed POSIXor dPOSIX for short.  
  What do I mean by this? Well, with whatever we come up for dPOSIX (besides, hopefully a better name) it will presumably have the following characteristics:
  
       
  •       Container as first-class citizens: no matter what the unit of scheduling is (Kubernetes had pods from the get-go, DC/OS is introducing it with 1.9, Docker will at some point likely follow?), dPOSIX will be treating      containersas first-class entities. For example, we can expect dPOSIX APIs will understand how to express to run different types of distributed processes—such as long-running ones or batch jobs—using different container runtimes, from the currently dominating Docker to AppC and OCI.   
  •       Distributed runtime environment: dPOSIX will assume a bunch of nodes (aka cluster or cell or datacenter) as the runtime environment; doesn’t matter if you’re talking about 10 (most of us) or 100,000 (some big ones) nodes. Some of the implications being: 1. software defined networking is front and center, 2. cattle (mostly) and some pets (as a safety blanket, for ‘legacy apps’), and 3. immutable infrastructure on all levels (from node to service/function). The only two questions left are: how long will you push back for going all in concerning public cloud (more below), and how to minimize cloud provider lock-in (hint: container orchestration systems allow you to be agnostic about it) where possible.   
  •       DevOps is the default: dPOSIX requires to re-think the roles and responsibilities how we build and operate services and applications. Increasingly, cloud native deployments at least blur the line between developers and operations and in the extreme case (      serverless, erm, Function-as-a-Service) require that the person who wrote some code is also responsible for operating it in prod.  



上一篇:微服务化改造(一):总览
下一篇:Proof You Can Become a Better Programmer
林若思 发表于 2016-11-27 19:26:38
你女儿在我手上,我不是你女婿。
回复 支持 反对

使用道具 举报

biopig 发表于 2016-12-4 03:43:04
檐铃伴风夜成眠有内涵!
回复 支持 反对

使用道具 举报

翠翠 发表于 2016-12-4 06:08:46
你知道得太多了
回复 支持 反对

使用道具 举报

*滑动验证:
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

我要投稿

推荐阅读


回页顶回复上一篇下一篇回列表
手机版/CoLaBug.com ( 粤ICP备05003221号 | 文网文[2010]257号 )

© 2001-2017 Comsenz Inc. Design: Dean. DiscuzFans.

返回顶部 返回列表