Filestream Best practices...

Hi All;
 I thought I would reach out to all my spicehead DBA's for some helpful insight...We are in the middle of revamping our front end code (Structure of the database will remain intact and unchanged for the most part...read on); Coding it out in another language and nearly complete when reviewing some best practices we had some internal questions brought up that isn't really covered online as far as we can search.  Current we store all our documents (office and pdf's) inside the DB as BLOB Data and we want to move this to Filestream structure having said that the documents are sort of a separate part of our system where queries don't normally interact with the document table unless explicitly asked so would we find a noticeable degradation in performance if we isolate that filestream portion into its own DB? And part two of this would be the filestream data itself, would you store them on the same server as the SQL server and if the answer is yes would you use a separate storage drive to do so or stick it all with the SQL DB's?  Space concerns are nil as resources and additional servers required if that's the best solution...we just want to be sure it's the most sound solution for the application.   Current projections are BLOB Data with the DB will reach a TB in 3 months extend forecasts are 500 to 700GB a year for the filestream data. Just to give you some insight of what we are dealing with. Nothing extraordinary but any stretch of the imagination. Just a typical setup in my mind.