mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
translating
This commit is contained in:
geekpi
parent
3f0071b742
commit
6062e212a9
@ -1,64 +0,0 @@
|
||||
[#]: subject: "What cloud developers need to know about hardware"
|
||||
[#]: via: "https://opensource.com/article/23/3/cloud-hardware"
|
||||
[#]: author: "Jay Faulkner https://opensource.com/users/jayf"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
What cloud developers need to know about hardware
|
||||
======
|
||||
|
||||
It's easy to forget the progress that people in tech have made. In the early 2000s, most local user groups held regular install fests. Back then, to configure a single machine to run Linux well, we had to know intimate details about hardware and how to configure it. Now, almost twenty years later, we represent a project whose core ideal is to make getting a single computer to run Linux as easy as an API call. In this new world, operators and developers alike no longer have to worry about the hardware in their servers. This change has had a profound impact on the next generation of operators and developers.
|
||||
|
||||
In the early days of computer technology, you had to put your hands on the hardware frequently. If a computer needed more memory, you just added it. As time passed, technology also evolved in big ways. This ended up moving the operator further from the hardware. What used to be a trip to the data center is now a support ticket to have remote hands on the hardware. Eventually, hardware was disposed of altogether. Instead, you now summon and destroy "servers" with simple commands and no longer have to worry about hardware.
|
||||
|
||||
Here is the real truth: hardware exists because it is needed to power clouds. But what is a cloud, really?
|
||||
|
||||
### Why hardware is critical to the cloud
|
||||
|
||||
A cloud is a centralization of foundational resources built upon utilizing abstractions. It can range from being as simple as a hypervisor running a few VMs in your [homelab][1] to levels of complexity that include custom servers, networking gear, containers, and technology that's been designed from the ground up to focus on efficiencies of scale.
|
||||
|
||||
They are nebulous. They evolve.
|
||||
|
||||
Those entering technology today don't have the same hands-on experiences as more experienced developers had. Many are trained to use clouds from their earliest interactions with computers. They don't know a world without a button to change the memory allocation. They can point their attention to higher levels in the technology stack. Yet without an understanding of the foundations the infrastructure they use is built upon, they are implicitly giving away their opportunity to learn the lower levels of the stack, including hardware. No fault exists here because the implementer and operator of the cloud infrastructure have made specific choices to intentionally make their products easier to use.
|
||||
|
||||
This means that now, more than ever, you have to think intentionally about what trade-offs you make — or others make — when choosing to use cloud technologies. Most people will not know what trade-offs have been made until they get their first oversized cloud bill or first outage caused by a "noisy neighbor". Can businesses trust their vendors to make trade-offs that are best for their operations? Will vendors suggest more efficient or more profitable services? Let the buyer (or engineer!) beware.
|
||||
|
||||
**[ Related read [5 things open source developers should know about cloud services providers][2] ]**
|
||||
|
||||
Thinking intentionally about trade-offs requires looking at your requirements and goals from multiple perspectives. Infrastructure decisions and the trade-offs therein are inherent to the overall process, design, or use model for that project. This is why they must be planned for as soon as possible. Multiple different paths must be considered in order to find your project a good home.
|
||||
|
||||
First, there is the axis of the goal to be achieved, or the service provided. This may come with requirements around speed, quality, or performance. This can in itself drive a number of variables. You may need specialized hardware such as GPUs to process a request with acceptable speed. Will this workload need to auto-scale, or not? Of course, these paths are intertwined. The question already jumps to "Will my wallet auto-scale?"
|
||||
|
||||
Business requirements are another part of this to consider. Your project may have specific security or compliance requirements which dictate where data is stored. Proximity to related services is also a potential concern. This includes ensuring a [low-latency connection][3] to a nearby stock exchange or ability to provide a high-quality local video cache as part of a content delivery network.
|
||||
|
||||
Then there is the final part which is the value and cost of the service provided — how much one wishes to or can spend to meet the requirements. This is tightly bound with the first path. The "what" your business is and "how" your business operates. This can be something as mundane as whether your business prefers CapEx versus OpEx.
|
||||
|
||||
**[ Also read [Cloud services: 4 ways to get the most from your committed spend][4] ]**
|
||||
|
||||
When looking at these options it is easy to see how changing any one variable can begin to change the other variables. They are inherently intertwined, and some technologies may allow for these variables to shift dynamically. Without understanding lower layers of substrate, you risk taking paths that further this dynamic model of billing. For some, this is preferred. For others, it can be dreaded.
|
||||
|
||||
Even though learning hardware-specific knowledge has become more optional in modern technology stacks, we hope this article has encouraged you to look into what you may be missing out on without even knowing. Hardware improvements have been a large part of feature delivery and efficiency gains, shrinking computers from room-sized monstrosities to small enough to implant inside a human. We hope you take time to stop, learn, and consider what hardware platform your next project will be running on, even if you don't control it.
|
||||
|
||||
If you are a student who hasn't gotten their head out of the clouds yet, go find an [old computer][5], install a stick of RAM, and challenge yourself to learn something new.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/23/3/cloud-hardware
|
||||
|
||||
作者：[Jay Faulkner][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jayf
|
||||
[b]: https://github.com/lkxed/
|
||||
[1]: https://www.redhat.com/sysadmin/linux-homelab-rhel?intcmp=7013a000002qLH8AAM
|
||||
[2]: https://opensource.com/article/22/3/cloud-services-providers
|
||||
[3]: https://enterprisersproject.com/article/2022/5/edge-computing-latency-matters?intcmp=7013a000002qLH8AAM
|
||||
[4]: https://enterprisersproject.com/article/2022/8/cloud-services-get-most-your-committed-spend?intcmp=7013a000002qLH8AAM
|
||||
[5]: https://opensource.com/article/22/4/how-linux-saves-earth
|
||||
@ -0,0 +1,58 @@
|
||||
[#]: subject: "What cloud developers need to know about hardware"
|
||||
[#]: via: "https://opensource.com/article/23/3/cloud-hardware"
|
||||
[#]: author: "Jay Faulkner https://opensource.com/users/jayf"
|
||||
[#]: collector: "lkxed"
|
||||
[#]: translator: "geekpi"
|
||||
[#]: reviewer: " "
|
||||
[#]: publisher: " "
|
||||
[#]: url: " "
|
||||
|
||||
云开发人员需要了解的硬件知识
|
||||
======
|
||||
|
||||
我们很容易忘记科技界人士所取得的进步。在 2000 年代初期，大多数本地用户组定期举行安装节。那时，要配置一台机器来很好地运行 Linux，我们必须了解有关硬件的详细信息以及如何配置它。现在，将近二十年后，我们代表了一个项目，其核心理想是让一台计算机运行 Linux 就像 API 调用一样简单。在这个新世界中，运营商和开发者等不再需要担心服务器中的硬件。这种变化对下一代的运营商和开发者产生了深远的影响。
|
||||
|
||||
在计算机技术的早期，你不得不经常上手硬件。如果计算机需要更多内存，你只需添加它即可。随着时间的推移，技术也有了很大的发展。这最终使操作员远离硬件。过去需要去数据中心一趟，现在变成了远程操作硬件的支持工单。最终，硬件被完全处理掉了。相反，你现在可以通过简单的命令召唤和摧毁“服务器”，而不必再担心硬件问题。
|
||||
|
||||
这里是真正的真相：硬件的存在是因为需要它来为云提供动力。但是，云到底是什么？
|
||||
|
||||
### 为什么硬件对云至关重要
|
||||
|
||||
云是建立在利用抽象之上的基础资源的集中。它的范围可以从简单到在你的[家庭实验室][1]中运行几个虚拟机的管理程序，到包括定制服务器、网络设备、容器和从头开始设计的专注于规模效率的技术等复杂程度。
|
||||
|
||||
它们是模糊的。它们在进化。
|
||||
|
||||
今天那些进入技术领域的人没有像更有经验的开发人员那样的实践经验。许多人从最早与计算机交互时就接受过使用云的培训。他们不知道没有按钮来更改内存分配的世界。他们可以将注意力转移到技术栈的更高层次。然而，如果不了解他们所使用的基础架构所建立的基础，他们就会含蓄地放弃学习栈较低级别（包括硬件）的机会。这里不存在错误，因为云基础设施的实施者和运营商已经做出了特定的选择，有意让他们的产品更易于使用。
|
||||
|
||||
这意味着现在，你比以往任何时候都更需要有意识地考虑在选择使用云技术时你或其他人做出的权衡。大多数人在收到第一份超额云账单或第一次因“吵闹的邻居”造成的中断之前，不会知道已经做出了哪些权衡。企业能否信任他们的供应商做出最适合他们运营的权衡？ 供应商会建议更有效或更有利可图的服务吗？ 让买家（或工程师！）当心。
|
||||
|
||||
有意识地考虑权衡取舍需要从多个角度审视你的要求和目标。基础设施决策和其中的权衡是该项目的整个过程、设计或使用模型所固有的。这就是为什么必须尽快计划它们的原因。必须考虑多种不同的路径，以便为你的项目找到一个合适的归宿。
|
||||
|
||||
首先，是要实现的目标或提供的服务的轴心。这可能伴随着速度、质量或性能方面的要求。这本身可以驱动许多变量。你可能需要专用硬件（例如 GPU）才能以可接受的速度处理请求。此负载是否需要自动缩放？ 当然，这些路径是交织在一起的。问题已经跳转到“我的钱包会自动缩放吗？”
|
||||
|
||||
业务需求是要考虑的另一部分。你的项目可能有特定的安全或合规性要求，这些要求规定了数据的存储位置。邻近相关服务也是一个潜在的问题。这包括确保与附近证券交易所的[低延迟连接][3]或能够提供高质量的本地视频缓存作为内容交付网络的一部分。
|
||||
|
||||
然后是最后一部分，即所提供服务的价值和成本：一个人希望或可以花多少钱来满足要求。这与第一条路径紧密相关。你的业务是“什么”以及你的业务“如何”运作。这可以像你的企业更喜欢资本支出还是更喜欢运营支出一样平凡。
|
||||
|
||||
当看到这些选项时，很容易看到改变任何一个变量都会开始改变其他变量。它们在本质上是相互交织的，一些技术可能允许这些变量动态变化。如果不了解较低层次的底层，你就有可能采取推动这种动态计费模式的路径。对一些人来说，这是首选。对其他人来说，这可能是令人恐惧的。
|
||||
|
||||
尽管在现代技术栈中，学习特定的硬件知识已变得更加可有可无，但我们希望这篇文章能鼓励你去研究你可能在不知不觉中错过的东西。硬件的改进是功能交付和效率提高的一个重要部分，将计算机从房间大小的怪物缩小到小到可以植入人体内。我们希望你花时间停下来，学习并考虑你的下一个项目将在什么硬件平台上运行，即使你不控制它。
|
||||
|
||||
如果你是一个还没有把头从云端拿出来的学生，去找一台[旧电脑][5]，安装一根内存，挑战自己，学习新东西。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/23/3/cloud-hardware
|
||||
|
||||
作者：[Jay Faulkner][a]
|
||||
选题：[lkxed][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/jayf
|
||||
[b]: https://github.com/lkxed/
|
||||
[1]: https://www.redhat.com/sysadmin/linux-homelab-rhel?intcmp=7013a000002qLH8AAM
|
||||
[3]: https://enterprisersproject.com/article/2022/5/edge-computing-latency-matters?intcmp=7013a000002qLH8AAM
|
||||
[5]: https://opensource.com/article/22/4/how-linux-saves-earth
|
||||
Loading…
Reference in New Issue
Block a user