3.2. More options to protect script 1.3.3. More options to protect package 1.3.4. Copying package data files 1.3.5. Checking runtime key periodically 1.3.6. Binding to many machines 1.3.7. Using outer different applications 2.1.4. Reforming scripts to improve security 2.2. Protecting Runtime Memory Data 2.3. Packing with outer key 2.4. Building obfuscated wheel 2.5. Protecting system packages 2.6. Fix 3.2. More options to protect script 1.3.3. More options to protect package 1.3.4. Copying package data files 1.3.5. Checking runtime key periodically 1.3.6. Binding to many machines 1.3.7. Using outer

scale & load balancing High availability w/auto patching Reduced operations costs Backup & recovery Global data center footprint Hybrid support Azure Active Directory integration Secure & compliance

Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault- tolerant Excellent configurable error recovery when using RabbitMQ, ensures your tasks are never lost. scenarios, and your tasks will never be they’re not used – Avoid launching synchronous subtasks • Performance and Strategies – Granularity – Data locality – State – Database transactions • Example – blog/models.py – blog/views.py – blog/tasks processing other waiting tasks. However, executing a task does have overhead. A message needs to be sent, data may not be local, etc. So if the tasks are too fine-grained the additional overhead may not be worth

Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault- tolerant Excellent configurable error recovery when using RabbitMQ, ensures your tasks are never lost. scenarios, and your tasks will never be they’re not used – Avoid launching synchronous subtasks • Performance and Strategies – Granularity – Data locality – State – Database transactions • Example – blog/models.py – blog/views.py – blog/tasks processing other waiting tasks. However, executing a task does have overhead. A message needs to be sent, data may not be local, etc. So if the tasks are too fine-grained the additional overhead may not be worth

Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault-tolerant Excellent configurable error recovery when using RabbitMQ, ensures your tasks are never lost. scenarios, and your tasks will never be if they’re not used Avoid launching synchronous subtasks Performance and Strategies Granularity Data locality State Database transactions Example blog/models.py blog/views.py blog/tasks.py This guide processing other waiting tasks. However, executing a task does have overhead. A message needs to be sent, data may not be local, etc. So if the tasks are too fine-grained the additional overhead may not be worth

Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault- tolerant Excellent configurable error recovery when using RabbitMQ, ensures your tasks are never lost. Dis- tributed Runs on one or more machines Using Redis Redis is also feature-complete, but power failures or abrupt termination may result in data loss. • Using SQLAlchemy • Using the Django Database Using a database as a message queue is not they’re not used – Avoid launching synchronous subtasks • Performance and Strategies – Granularity – Data locality – State – Database transactions • Example – blog/models.py – blog/views.py – blog/tasks

Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault-tolerant Excellent configurable error recovery when using RabbitMQ, ensures your tasks are never lost. scenarios, and your tasks will never be if they’re not used Avoid launching synchronous subtasks Performance and Strategies Granularity Data locality State Database transactions Example blog/models.py blog/views.py blog/tasks.py This guide processing other waiting tasks. However, executing a task does have overhead. A message needs to be sent, data may not be local, etc. So if the tasks are too fine-grained the additional overhead may not be worth

Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault-tolerant Excellent configurable error recovery when using RabbitMQ, ensures your tasks are never lost. Distributed Runs on one or more machines [http://redis.io/] is also feature-complete, but power failures or abrupt termination may result in data loss. Using SQLAlchemy Using the Django Database Using a database as a message queue is not recommended if they’re not used Avoid launching synchronous subtasks Performance and Strategies Granularity Data locality State Database transactions Example blog/models.py blog/views.py blog/tasks.py This guide

Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault- tolerant Excellent configurable error recovery when using RabbitMQ, ensures your tasks are never lost. Dis- tributed Runs on one or more machines Using Redis Redis is also feature-complete, but power failures or abrupt termination may result in data loss. • Using SQLAlchemy • Using the Django Database Using a database as a message queue is not they’re not used – Avoid launching synchronous subtasks • Performance and Strategies – Granularity – Data locality – State – Database transactions • Example – blog/models.py – blog/views.py – blog/tasks

Beanstalk, MongoDB, CouchDB, and popular SQL databases. Fault-tolerant Excellent configurable error recovery when using RabbitMQ, ensures your tasks are never lost. Distributed Runs on one or more machines [http://redis.io/] is also feature-complete, but power failures or abrupt termination may result in data loss. Using SQLAlchemy Using the Django Database Using a database as a message queue is not recommended if they’re not used Avoid launching synchronous subtasks Performance and Strategies Granularity Data locality State Database transactions Example blog/models.py blog/views.py blog/tasks.py This guide