asp.net - Similarity of Connection pooling in ADO.NET and Throttling in WCF -

can explain me connection pooling in ado.net , throttling in wcf same.

they seem similar.

sql connection pooling reusing.

connecting database server typically consists of several time-consuming steps. physical channel such socket or named pipe must established, initial handshake server must occur, connection string information must parsed, connection must authenticated server, checks must run enlisting in current transaction, , on.

in practice, applications use 1 or few different configurations connections. means during application execution, many identical connections repeatedly opened , closed. to minimize cost of opening connections, ado.net uses optimization technique called connection pooling.

connection pooling reduces number of times new connections must opened. pooler maintains ownership of physical connection. manages connections keeping alive set of active connections each given connection configuration. whenever user calls open on connection, pooler looks available connection in pool. if pooled connection available, returns caller instead of opening new connection.

wcf throttling limiting how many service instances or sessions created @ application level.

the main purpose throttling settings can classified following 2 aspects:

1. controlled resource usage: throttling of concurrent execution, usage of resources such memory or threads can limited reasonable level system works without hitting reliability issues.
2. balanced performance load: systems work in balanced way when load controlled. if there concurrent execution happening, lot of contention , bookkeeping happen , hurt performance of system.

two different concepts serving 2 different purposes.