mirror of
https://github.com/LCTT/TranslateProject.git
synced 2024-12-29 21:41:00 +08:00
translated
This commit is contained in:
geekpi
parent
945e51173a
commit
93cac48ad9
@ -1,55 +0,0 @@
|
||||
translating---geekpi
|
||||
|
||||
[How to deploy multi-cloud serverless and Cloud Foundry APIs at scale][2]
|
||||
============================================================
|
||||
|
||||
“Micro-services and APIs are products and we need to think about them that way,” says IBM’s Ken Parmelee.
|
||||
|
||||
|
||||
|
||||
Ken Parmelee, who leads the API gateway for IBM and Big Blue’s open source projects, has a few ideas about open-source methods for “attacking” the API and how to create micro-services and make them scale.
|
||||
|
||||
“Micro-services and APIs are products and we need to be thinking about them that way,” Parmelee says. “As you start to put them up people rely on them as part of their business. That’s a key aspect of what you’re doing in this space.”
|
||||
|
||||
|
||||
|
||||
He took the stage at the recent [Nordic APIs 2017 Platform Summit][3] and challenged a few popular notions.
|
||||
|
||||
“Fail fast is not really a good concept. You want to get something out there that’s fantastic on the first run. That doesn’t mean you need to take tons of time, but make it fantastic then keep evolving and improving. If it’s really bad in the beginning, people aren’t going to want to stick with you.”
|
||||
|
||||
He runs through IBM’s modern serverless architectures including [OpenWhisk][4], an open source partnership between IBM and Apache. The cloud-first distributed event-based programming service is result of focusing on this space for over two years; IBM is a leading contributor and it serves as the foundation of IBM cloud functions. It offers infrastructure-as-a-service, automatically scales, offers support for multiple languages and users pay only for what they actually use. Challenges were also a part of this journey, as they discovered that servers actions need securing and require ease — anonymous access, missing usage trails, fixed URL schemes etc.
|
||||
|
||||
Anyone can try out these serverless APIs in just 30 seconds at [https://console.bluemix.net/openwhisk/][5] “This sounds very gimmicky, but it is that easy to do…We’re combining the [work we’ve done with Cloud Foundry ][6]and released them in Bluemix under the OpenWhisk to provide security and scalability.”
|
||||
|
||||
“Flexibility is also hugely important for micro-services,” he says. “When you’re working in the real world with APIs, you start to have to scale across clouds.” That means from your on-premise cloud to the public cloud and “having an honest concept of how you’re going to do that is important.
|
||||
|
||||
|
||||
|
||||
And when thinking about the “any cloud concept” he warns that it’s not “throw it into any Docker container and it runs anywhere. That’s great but it needs to run effectively in those environments. Docker and Kubernetes help a lot, but you want to operationalize how you’re going to do it.” Think ahead on the consumption of your API – whether it’s running only internally or will expand to a public cloud and be publicly consumable – you need have that “architectural view,” he adds.
|
||||
|
||||
“We all hope that what we create has value and gets consumed a lot,” Parmelee says. The more successful the API, the bigger the challenge of taking it to the next level.
|
||||
|
||||
APIs are building blocks for micro-services or “inter-services.”
|
||||
|
||||
The future of APIs is cloud native — regardless of where you start, he says. Key factors are scalability, simplifying back-end management, cost and avoiding vendor lock-in.
|
||||
|
||||
You can catch his entire 23-minute talk below or on [YouTube][7].
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://superuser.openstack.org/articles/deploy-multi-cloud-serverless-cloud-foundry-apis-scale/
|
||||
|
||||
作者：[Superuser ][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://superuser.openstack.org/articles/author/superuser/
|
||||
[1]:http://superuser.openstack.org/articles/author/superuser/
|
||||
[2]:http://superuser.openstack.org/articles/deploy-multi-cloud-serverless-cloud-foundry-apis-scale/
|
||||
[3]:https://nordicapis.com/events/the-2017-api-platform-summit/
|
||||
[4]:https://developer.ibm.com/openwhisk/
|
||||
[5]:https://console.bluemix.net/openwhisk/
|
||||
[6]:https://cloudfoundry.org/the-foundry/ibm-cloud/
|
||||
[7]:https://www.youtube.com/jA25Kmxr6fU
|
||||
@ -0,0 +1,53 @@
|
||||
[如何成规模地部署多个云无服务器程序和 Cloud Foundry API] [2]
|
||||
============================================================
|
||||
|
||||
IBM 的 Ken Parmelee 说：“微服务和 API 是产品，我们需要以这种方式思考。”
|
||||
|
||||
|
||||
|
||||
领导 IBM API 网关和 Big Blue 开源项目的的 Ken Parmelee 对开源“攻击” API 方法以及如何创建微服务并伸缩有一些想法。
|
||||
|
||||
Parmelee说：“微服务和 API 是产品，我们需要以这种方式思考这些问题。当你开始这么做，人们依赖它作为它们业务的一部分。这是你在这个领域你做的关键方面”
|
||||
|
||||
|
||||
|
||||
他在最近的[北欧 API 2017 平台峰会][3]站上讲台，并挑战了一些流行的观念。
|
||||
|
||||
“快速失败不是一个很好的概念。你想在第一场比赛中获得一些非常棒的东西。这并不意味着你需要花费大量的时间，而是让它变得非常棒，然后不断的发展和改进。如果一开始真的很糟糕，人们就不会想要用你。”
|
||||
|
||||
他通过 IBM 的现代无服务器架构运行，包括 [OpenWhisk][4]，一个 IBM 和 Apache 之间的开源伙伴关系。 云优先分布式事件编程服务是两年多的重点关注这个领域的结果。IBM 是领先的贡献者，它是 IBM 云功能的基础。它提供基础设施即服务，自动缩放、为多种语言提供支持、用户只需支付实际使用费用。挑战也是这次旅程的一部分，因为他们发现服务器操作需要安全、并且需要轻松-匿名访问、缺少使用路径、固定的 URL 格式等。
|
||||
|
||||
任何人都可以在 [https://console.bluemix.net/openwhisk/][5] 上在 30 秒内尝试这些无服务器 API。“这听起来很有噱头, 但这是很容易做到的。我们正在结合[ Cloud Foundry 中完成的工作][6]，并在 OpenWhisk 下的 Bluemix 中发布了它们，以提供安全性和可扩展性。”
|
||||
|
||||
他说：“灵活性对于微服务也是非常重要的。 当你使用 API 在现实世界中工作时，你开始需要跨云进行扩展。”这意味着从你的内部云到公共云，并且对你要怎么做有一个诚实的概念很重要。
|
||||
|
||||
|
||||
|
||||
他警告说，在思考“任何云概念”的时候，不是“将其放入一个 Docker 容器，并到处运行。这很棒，但需要在这些环境中有效运行。Docker 和 Kubernetes 有提供了很多帮助，但是你想要你的操作方式付诸实施。” 提前考虑 API 的消耗，无论是在内部运行还是扩展到公有云并且可以公开消费 - 你需要有这样的“架构观”，他补充道。
|
||||
|
||||
Parmelee说：“我们都希望我们所创造的有价值，并被广泛使用。” API 越成功，将其提升到更高水平的挑战就越大。
|
||||
|
||||
API 是微服务或“服务间”的组成部分。
|
||||
|
||||
他说，API 的未来是原生云的 - 无论你从哪里开始。关键因素是可扩展性，简化后端管理，降低成本，避免锁定厂商。
|
||||
|
||||
你可以在下面或在 [YouTube][7] 观看他整整 23 分钟的演讲。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://superuser.openstack.org/articles/deploy-multi-cloud-serverless-cloud-foundry-apis-scale/
|
||||
|
||||
作者：[Superuser ][a]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:http://superuser.openstack.org/articles/author/superuser/
|
||||
[1]:http://superuser.openstack.org/articles/author/superuser/
|
||||
[2]:http://superuser.openstack.org/articles/deploy-multi-cloud-serverless-cloud-foundry-apis-scale/
|
||||
[3]:https://nordicapis.com/events/the-2017-api-platform-summit/
|
||||
[4]:https://developer.ibm.com/openwhisk/
|
||||
[5]:https://console.bluemix.net/openwhisk/
|
||||
[6]:https://cloudfoundry.org/the-foundry/ibm-cloud/
|
||||
[7]:https://www.youtube.com/jA25Kmxr6fU
|
||||
Loading…
Reference in New Issue
Block a user