"are global variables thread-safe in flask? how do i share data between requests?" Code Answer

you can't use global variables to hold this sort of data. not only is it not thread safe, it's not process safe, and wsgi servers in production spawn multiple processes. not only would your counts be wrong if you were using threads to handle requests, they would also vary depending on which process handled the request.

use a data source outside of flask to hold global data. a database, memcached, or redis are all appropriate separate storage areas, depending on your needs. if you need to load and access python data, consider multiprocessing.manager. you could also use the session for simple data that is per-user.

the development server may run in single thread and process. you won't see the behavior you describe since each request will be handled synchronously. enable threads or processes and you will see it. app.run(threaded=true) or app.run(processes=10). (in 1.0 the server is threaded by default.)

some wsgi servers may support gevent or another async worker. global variables are still not thread safe because there's still no protection against most race conditions. you can still have a scenario where one worker gets a value, yields, another modifies it, yields, then the first worker also modifies it.

if you need to store some global data during a request, you may use flask's g object. another common case is some top-level object that manages database connections. the distinction for this type of "global" is that it's unique to each request, not used between requests, and there's something managing the set up and teardown of the resource.