# Part V. Isolating tracker-store clients

Every user of tracker_sparql_connection_get() or tracker_sparql_connection_get_async() relies on an external tracker-store instance to maintain the database, and possibly on additional tracker miners to write the data consumed by the application.

Traditionally there has been only a single instance of tracker-store and miners, shared by all consumers of Tracker data. With Tracker 2.0 it became possible to let clients spawn their own sets of these services.