Best practices for connecting to Streaming API on production and dev servers?


#1

My question is relatively straightforward - I’ve got a single application registered with Twitter, for which I have a single set of API keys. I finally deployed my app to production, so now I have a single instance of the streaming API connected and running at all times.

I want to continue working on it, with access to the streaming API, on a dev server. There’s only a single developer working on it (me). Is it alright if I boot up a 2nd app server with a 2nd connection to the streaming API using these keys concurrently? Or should I register a new Twitter application (product_name-dev) for this purpose?

Thanks for any help in advance