concept client.conf file in category apache pulsar

This is an excerpt from Manning's book Apache Pulsar in Action.
Now that we have a MongoDB cluster running locally, and a database created we can proceed with configuring a MongoDB sink connector so that it will read messages from a Pulsar topic and write the messages into a MongoDB table we created.
Figure 5.9: Gaming sessions will publish data to the “Game Score” topic and consume from the “LeaderBoard” topic.
![]()
From a development perspective we face some challenges, for starters, our team is dependent upon the completion of the game sessions development, which will be providing the data feeds that our system relies on as its input data. Unfortunately, this is the single most complex piece of software in our gaming application, and consequently will not be available throughout the majority of our development phase. Obviously, we cannot wait for that development team, and are fortunate enough to have an agreed upon data format to work with. Therefore, we can use synthetic data throughout our development and testing phases. One approach would be to develop an application that simulates the generation of the scoring events by producing a series of random scoring events like the Source connector shown in Listing 5.8