Feature Request: TFS Integration Platform Multi-Node Scale Out
it'd useful spread load across multiple servers tfs integration platform using same database, e.g. 4 servers running integration service(s), single database, , ui on user workstations 'engineers' submit project migrations on behalf of users (and potentially manage bidirectional migrations with custom adaptors). spreading load increase performance of migrations.
scenario: small tfs instance based in ~50 projects in 1 tpc. users realise the large, centralised tfs infrastructure based in emea serve purposes more efficiently platform using. business unit smaller platform already has collection on centralised infrastructure, project need migrated tpc. pinchpoints in case network latency , processing capability of emea based platform.
using low spec'd dev. infrastructure 2 ats , 1 dt unbelievably slow, , appear integration platform doesn't process single project using 2 nodes (which, believe, increase throughput). on production infrastructure large scale data tier , 4 ats, processing could be more efficient, should integration platform support scaled-out implementaton (this also, potentially, run on own infrastructure).
is alm rangers commit to? make lot of sense when upgrade our 2010 platform 2012, , users want start using different process templates (e.g. migrating cmmi agile or scrum, migrating agile scrum, or scrum agile - depending on preferences, if do realise may lose fidelity within wis)
hi alfeersum,
thanks post!
do mean want upgrade tfs 2010 tfs 2012 , load across multiple servers tfs 2012 using same database?
best regards,
cathy kong [msft]
msdn community support | feedback us
Archived Forums V > Team Foundation Server – Migration and Integration
Comments
Post a Comment