EVERY ENTITY AS A MICROSERVICE taowen@gmail.com JOB WELL DONE! "The Mess We're In" by Joe Armstrong ■ In the last 40 years we have written billions of lines of code that will keep programmers Entity 1 Entity 2 Coordinate by communication (function call) ������� = ����� � � “����” ����� EVERY ENTITY AS AN ACTOR Microservice ����������� mysql Q/A

ONLINE TOOLS EVERY C++ DEVELOPER SHOULD KNOW Thamara AndradeHELLO! 2 https://thamara.dev @thamyk I am Thamara Andrade (she/her) Lead Software Engineer @ CadenceHELLO! 3 https://thamara.dev @thamyk

proveUndefined Behavior 21 Undefined vs unspecified ● C++ standard does not specify behavior of every program ● Undefined behavior: the entire program is ill-formed delete p; p foo(); → int Your program is designed and specified to produce certain results ● Results depend on inputs ● For every valid input, you must define corresponding results – This is the contract with the userUndefined Your program is designed and specified to produce certain results ● Results depend on inputs ● For every valid input, you must define corresponding results – This is the contract with the user ● You must

another. Trace- backs Errors and tracebacks are stored and can be investigated after the fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. No backend works well for every use case. You should read about the strengths and weaknesses of each backend, and choose the most states. There are several other pitfalls you should be aware of when using the AMQP backend: • Every new task creates a new queue on the server, with thousands of tasks the broker may be overloaded with

another. Trace- backs Errors and tracebacks are stored and can be investigated after the fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and task that re-indexes a search engine, and the search engine should only be re-indexed at maximum every 5 minutes, then it must be the tasks responsibility to assert that, not the callers. Another gotcha is no support for broker connection pools, so apply_async establishes and closes a new connection every time it is called. This is something you need to be aware of when sending more than one task at a

another. Tracebacks Errors and tracebacks are stored and can be investigated after the fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and task that re-indexes a search engine, and the search engine should only be re-indexed at maximum every 5 minutes, then it must be the tasks responsibility to assert that, not the callers. Another gotcha is no support for broker connection pools, so apply_async establishes and closes a new connection every time it is called. This is something you need to be aware of when sending more than one task at a

another. Trace- backs Errors and tracebacks are stored and can be investigated after the fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and MongoDB, Tokyo Tyrant and Redis – or you can define your own. There is no backend that works well for every single use case, but for historical reasons the default backend is the AMQP backend. You should read states. There are several other pitfalls you should be aware of when using the AMQP backend: • Every new task creates a new queue on the server, with thousands of tasks the broker may be overloaded with

synchronously (wait until ready). Celery is used in production systems to process millions of tasks every hour. 3 Celery Documentation, Release 2.5.5 Celery is written in Python, but the protocol can be another. Trace- backs Errors and tracebacks are stored and can be investigated after the fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. No backend works well for every use case. You should read about the strengths and weaknesses of each backend, and choose the most

another. Tracebacks Errors and tracebacks are stored and can be investigated after the fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and Redis, AMQP, MongoDB, Tokyo Tyrant and Redis – or you can define your own. No backend works well for every use case. You should read about the strengths and weaknesses of each backend, and choose the most new states. There are several other pitfalls you should be aware of when using the AMQP backend: Every new task creates a new queue on the server, with thousands of tasks the broker may be overloaded with

another. Tracebacks Errors and tracebacks are stored and can be investigated after the fact. UUID Every task has an UUID (Universally Unique Identifier), which is the task id used to query task status and MongoDB, Tokyo Tyrant and Redis – or you can define your own. There is no backend that works well for every single use case, but for historical reasons the default backend is the AMQP backend. You should read new states. There are several other pitfalls you should be aware of when using the AMQP backend: Every new task creates a new queue on the server, with thousands of tasks the broker may be overloaded with