Gopher  China  2015  Resource  Scheduling  &  Container  Technology  for  Financial  Service  动态资源管理和容器技术  在金融行业的架构探索和明天  余军  Gopher  China  2015  Gopher  China  2015  China  2015  求解之路的探索  n 他们是否解决了我们的问题?  n No   ① Mesos  采用了DRF(Dominant  Resource  Fairness)  调度机制。 YARN自带FIFO、Capacity  Scheduler和Fair  Scheduler(借鉴了 Mesos的DRF)。  ② Mes oop中Capacity  Scheduler的调度机制，将所有资源分成若干个queue，每个 queue分配一定量的资源，每个user有一定的资源使用上限。  ③ Mesos采用了Resource  Offer机制，这种调度机制面临着资源碎 片问题，即：每个节点上的资源不可能全部被分配完，剩下的一 点可能不足以让任何任务运行，这样，便产生了类似于操作系统 中的内存碎片问题。 

that take a user-suppiled lambda to generate the data needed to render our desired compile-time resource! These are e�ectively templated functions, but we will use the cleaner auto parameter syntax for

Free Pascal Resource support (FCL-res): Reference guide. Reference guide for FCL-res units. Document version 3.2.2 May 2021 Giulio Bernardi Contents 0.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 21 0.3 How to implement a new resource class . . . . . . . . . . . . . . . . . . . . . . . . 27 0.4 How to implement a new resource reader . . . . . . . . . . . . . . . . . . . . . . . . 31 0.5 How to implement a new resource writer . . . . . . . . . . . . . . . . . . . . . . . . 37 0.6 Format of resources in object files . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic HTTP error responses • Full Unicode support • Intuitive request Highly-optimized, extensible code base • Intuitive routing via URI templates and REST-inspired resource classes • Easy access to headers and bodies through request and response classes • DRY request process_response(self, req, resp, resource): if not hasattr(resp.context, 'result'): return resp.body = json.dumps(resp.context.result) def max_body(limit): def hook(req, resp, resource, params): length = req

effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic HTTP error responses • Full Unicode support • Intuitive request Highly-optimized, extensible code base • Intuitive routing via URI templates and REST-inspired resource classes • Easy access to headers and bodies through request and response classes • DRY request process_response(self, req, resp, resource): if 'result' not in resp.context: return resp.body = json.dumps(resp.context['result']) def max_body(limit): def hook(req, resp, resource, params): length = req.content_length

effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic HTTP error responses • Full Unicode support • Intuitive request Highly-optimized, extensible code base • Intuitive routing via URI templates and REST-inspired resource classes • Easy access to headers and bodies through request and response classes • DRY request process_response(self, req, resp, resource): if 'result' not in resp.context: return resp.body = json.dumps(resp.context['result']) def max_body(limit): def hook(req, resp, resource, params): length = req

effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic HTTP error responses • Full Unicode support • Intuitive request Highly-optimized, extensible code base • Intuitive routing via URI templates and REST-inspired resource classes • Easy access to headers and bodies through request and response classes • DRY request process_response(self, req, resp, resource): if 'result' not in resp.context: return resp.body = json.dumps(resp.context['result']) def max_body(limit): def hook(req, resp, resource, params): length = req

effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic HTTP error responses • Full Unicode support • Intuitive request authorize the request, taking into account the user’s role and the requested resource. Why doesn’t Falcon create a new Resource instance for every request? Falcon generally tries to minimize the number second to reduce memory usage. Therefore, when adding a route, Falcon requires an instance of your resource class, rather than the class type. That same instance will be used to serve all requests coming

Flask from flask_restful import Resource, Api app = Flask(__name__) api = Api(app) class HelloWorld(Resource): def get(self): return {'hello': 'world'} api.add_resource(HelloWorld, '/') if __name__ defining methods on your resource. A basic CRUD resource for a todo application (of course) looks like this: from flask import Flask, request from flask_restful import Resource, Api app = Flask(__name__) TodoSimple(Resource): def get(self, todo_id): return {todo_id: todos[todo_id]} def put(self, todo_id): todos[todo_id] = request.form['data'] return {todo_id: todos[todo_id]} api.add_resource(TodoSimple

Flask from flask_restful import Resource, Api app = Flask(__name__) api = Api(app) class HelloWorld(Resource): def get(self): return {'hello': 'world'} api.add_resource(HelloWorld, '/') if __name__ defining methods on your resource. A basic CRUD resource for a todo application (of course) looks like this: from flask import Flask, request from flask_restful import Resource, Api app = Flask(__name__) TodoSimple(Resource): def get(self, todo_id): return {todo_id: todos[todo_id]} def put(self, todo_id): todos[todo_id] = request.form['data'] return {todo_id: todos[todo_id]} api.add_resource(TodoSimple