mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-28 23:20:10 +08:00
Merge pull request #4117 from bazz2/master
[translated] Building Serverless App with Docker
This commit is contained in:
bazz2
GitHub
commit
a2c612d4e3
@ -1,100 +0,0 @@
|
||||
[bazz222222222]
|
||||
BUILDING SERVERLESS APPS WITH DOCKER
|
||||
======================================
|
||||
|
||||
Every now and then, there are waves of technology that threaten to make the previous generation of technology obsolete. There has been a lot of talk about a technique called “serverless” for writing apps. The idea is to deploy your application as a series of functions, which are called on-demand when they need to be run. You don’t need to worry about managing servers, and these functions scale as much as you need, because they are called on-demand and run on a cluster.
|
||||
|
||||
But serverless doesn’t mean there is no Docker – in fact, Docker is serverless. You can use Docker to containerize these functions, then run them on-demand on a Swarm. Serverless is a technique for building distributed apps and Docker is the perfect platform for building them on.
|
||||
|
||||
### From servers to serverless
|
||||
|
||||
So how might we write applications like this? Let’s take our example [a voting application consisting of 5 services][1]:
|
||||
|
||||
|
||||
|
||||
This consists of:
|
||||
|
||||
- Two web frontends
|
||||
- A worker for processing votes in the background
|
||||
- A message queue for processing votes
|
||||
- A database
|
||||
|
||||
The background processing of votes is a very easy target for conversion to a serverless architecture. In the voting app, we can run a bit of code like this to run the background task:
|
||||
|
||||
```
|
||||
import dockerrun
|
||||
client = dockerrun.from_env()
|
||||
client.run("bfirsh/serverless-record-vote-task", [voter_id, vote], detach=True)
|
||||
```
|
||||
|
||||
The worker and message queue can be replaced with a Docker container that is run on-demand on a Swarm, automatically scaling to demand.
|
||||
|
||||
We can even eliminate the web frontends. We can replace them with Docker containers that serve up a single HTTP request, triggered by a lightweight HTTP server that spins up Docker containers for each HTTP request. The heavy lifting has now moved the long-running HTTP server to Docker containers that run on-demand, so they can automatically scale to handle load.
|
||||
|
||||
Our new architecture looks something like this:
|
||||
|
||||
|
||||
|
||||
The red blocks are the continually running services and the green blocks are Docker containers that are run on-demand. This application has fewer long-running services that need managing, and by its very nature scales up automatically in response to demand (up to the size of your Swarm!).
|
||||
|
||||
### So what can we do with this?
|
||||
|
||||
There are three useful techniques here which you can use in your apps:
|
||||
|
||||
1. Run functions in your code as on-demand Docker containers
|
||||
2. Use a Swarm to run these on a cluster
|
||||
3. Run containers from containers, by passing a Docker API socket
|
||||
|
||||
|
||||
With the combination of these techniques, this opens up loads of possibilities about how you can architect your applications. Running background work is a great example of something that works well, but a whole load of other things are possible too, for example:
|
||||
|
||||
- Launching a container to serve user-facing HTTP requests is probably not practical due to the latency. However – you could write a load balancer which knew how to auto-scale its own web frontends by running containers on a Swarm.
|
||||
- A MongoDB container which could introspect the structure of a Swarm and launch the correct shards and replicas.
|
||||
|
||||
### What’s next
|
||||
|
||||
We’ve got all these radically new tools and abstractions for building apps, and we’ve barely scratched the surface of what is possible with them. We’re still building applications like we have servers that stick around for a long time, not for the future where we have Swarms that can run code on-demand anywhere in your infrastructure.
|
||||
|
||||
This hopefully gives you some ideas about what you can build, but we also need your help. We have all the fundamentals to be able to start building these applications, but its still in its infrancy – we need better tooling, libraries, example apps, documentation, and so on.
|
||||
|
||||
[This GitHub repository has links off to tools, libraries, examples, and blog posts][3]. Head over there if you want to learn more, and please contribute any links you have there so we can start working together on this.
|
||||
|
||||
Get involved, and happy hacking!
|
||||
|
||||
### Learn More about Docker
|
||||
|
||||
- New to Docker? Try our 10 min [online tutorial][4]
|
||||
- Share images, automate builds, and more with [a free Docker Hub account][5]
|
||||
- Read the Docker [1.12 Release Notes][6]
|
||||
- Subscribe to [Docker Weekly][7]
|
||||
- Sign up for upcoming [Docker Online Meetups][8]
|
||||
- Attend upcoming [Docker Meetups][9]
|
||||
- Watch [DockerCon EU 2015 videos][10]
|
||||
- Start [contributing to Docker][11]
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://blog.docker.com/2016/06/building-serverless-apps-with-docker/
|
||||
|
||||
作者：[Ben Firshman][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://blog.docker.com/author/bfirshman/
|
||||
|
||||
[1]: https://github.com/docker/example-voting-app
|
||||
[3]: https://github.com/bfirsh/serverless-docker
|
||||
[4]: https://docs.docker.com/engine/understanding-docker/
|
||||
[5]: https://hub.docker.com/
|
||||
[6]: https://docs.docker.com/release-notes/
|
||||
[7]: https://www.docker.com/subscribe_newsletter/
|
||||
[8]: http://www.meetup.com/Docker-Online-Meetup/
|
||||
[9]: https://www.docker.com/community/meetup-groups
|
||||
[10]: https://www.youtube.com/playlist?list=PLkA60AVN3hh87OoVra6MHf2L4UR9xwJkv
|
||||
[11]: https://docs.docker.com/contributing/contributing/
|
||||
|
||||
|
||||
|
||||
@ -0,0 +1,98 @@
|
||||
用 docker 创建 serverless 应用
|
||||
======================================
|
||||
|
||||
当今世界会时不时地出现一波科技浪潮，将以前的技术拍死在海滩上。针对 serverless 应用的概念我们已经谈了很多，它是指将你的应用程序按功能来部署，这些功能在被用到时才会启动。你不用费心去管理服务器和程序规模，因为它们会在需要的时候在一个集群中启动并运行。
|
||||
|
||||
但是 serverless 并不意味着没有 Docker 什么事儿，事实上 Docker 就是 serverless 的。你可以使用 Docker 来容器化这些功能，然后在 Swarm 中按需求来运行它们。Serverless 是一项构建分布式应用的技术，而 Docker 是它们完美的构建平台。
|
||||
|
||||
### 从 servers 到 serverless
|
||||
|
||||
那如何才能写一个 serverless 应用呢？来看一下我们的例子，[5个服务组成的投票系统][1]：
|
||||
|
||||
|
||||
|
||||
投票系统由下面5个服务组成：
|
||||
|
||||
- 两个 web 前端
|
||||
- 一个后台处理投票的进程
|
||||
- 一个计票的消息队列
|
||||
- 一个数据库
|
||||
|
||||
后台处理投票的进程很容易转换成 serverless 构架，我们可以使用以下代码来实现：
|
||||
|
||||
```
|
||||
import dockerrun
|
||||
client = dockerrun.from_env()
|
||||
client.run("bfirsh/serverless-record-vote-task", [voter_id, vote], detach=True)
|
||||
```
|
||||
|
||||
这个投票处理进程和消息队列可以用运行在 Swarm 上的 Docker 容器来代替，并实现按需自动部署。
|
||||
|
||||
我们也可以用容器替换 web 前端，使用一个轻量级 HTTP 服务器来触发容器响应一个 HTTP 请求。Docker 容器代替长期运行的 HTTP 服务器来挑起响应请求的重担，这些容器可以自动扩容来支撑大访问量。
|
||||
|
||||
新的架构就像这样：
|
||||
|
||||
|
||||
|
||||
红色框内是持续运行的服务，绿色框内是按需启动的容器。这个架构提供更少的长期运行服务让你管理，并且可以自动扩容（最大容量由你的 Swarm 决定）。
|
||||
|
||||
### 我们可以做点什么？
|
||||
|
||||
你可以在你的应用中使用3种技术：
|
||||
|
||||
1. 在 Docker 容器中按需运行代码。
|
||||
2. 使用 Swarm 来部署集群。
|
||||
3. 通过使用 Docker API 套接字在容器中运行容器。
|
||||
|
||||
结合这3种技术，你可以有很多方法搭建你的应用架构。用这种方法来部署后台环境真是非常有效，而在另一些场景，也可以这么玩，比如说：
|
||||
|
||||
- 由于存在延时，使用容器实现面向用户的 HTTP 请求可能不是很合适，但你可以写一个负载均衡器，使用 Swarm 来对自己的 web 前端进行自动扩容。
|
||||
- 实现一个 MongoDB 容器，可以自检 Swarm 并且启动正确的分片和副本（LCTT 译注：分片技术为大规模并行检索提供支持，副本技术则是为数据提供冗余）。
|
||||
|
||||
### 下一步怎么做
|
||||
|
||||
我们提供了这些前卫的工具和概念来构建应用，并没有深入发掘它们的功能。我们的架构里还是存在长期运行的服务，将来我们需要使用 Swarm 来把所有服务都用按需扩容的方式实现
|
||||
|
||||
希望本文能在你搭建架构时给你一些启发，但我们还是需要你的帮助。我们提供了所有的基本工具，但它们还不是很完善，我们需要更多更好的工具、库、应用案例、文档以及其他资料。
|
||||
|
||||
[我们在这里发布了工具、库和文档][3]。如果想了解更多，请移步到那里，另外请贡献一些链接给我们，这样我们就能一直工作了。
|
||||
|
||||
玩得愉快。
|
||||
|
||||
### 更多关于 Docker 的资料
|
||||
|
||||
- New to Docker? Try our 10 min [online tutorial][4]
|
||||
- Share images, automate builds, and more with [a free Docker Hub account][5]
|
||||
- Read the Docker [1.12 Release Notes][6]
|
||||
- Subscribe to [Docker Weekly][7]
|
||||
- Sign up for upcoming [Docker Online Meetups][8]
|
||||
- Attend upcoming [Docker Meetups][9]
|
||||
- Watch [DockerCon EU 2015 videos][10]
|
||||
- Start [contributing to Docker][11]
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://blog.docker.com/2016/06/building-serverless-apps-with-docker/
|
||||
|
||||
作者：[Ben Firshman][a]
|
||||
译者：[bazz2](https://github.com/bazz2)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://blog.docker.com/author/bfirshman/
|
||||
|
||||
[1]: https://github.com/docker/example-voting-app
|
||||
[3]: https://github.com/bfirsh/serverless-docker
|
||||
[4]: https://docs.docker.com/engine/understanding-docker/
|
||||
[5]: https://hub.docker.com/
|
||||
[6]: https://docs.docker.com/release-notes/
|
||||
[7]: https://www.docker.com/subscribe_newsletter/
|
||||
[8]: http://www.meetup.com/Docker-Online-Meetup/
|
||||
[9]: https://www.docker.com/community/meetup-groups
|
||||
[10]: https://www.youtube.com/playlist?list=PLkA60AVN3hh87OoVra6MHf2L4UR9xwJkv
|
||||
[11]: https://docs.docker.com/contributing/contributing/
|
||||
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user