Solution Deployment/Retraction and Feature Activation/Deactivation internal process flow

When you deploy/retract SharePoint WSPs and Activate/Deactivate site collection or sub site level features at the farm level using PowerShell commands or activate/deactivate features from browser interface, SharePoint 2010 makes several changes at the different places on the servers and databases.









Lets see what really happens when you execute different farm level PowerShell commands.

	Central Admin	Site/Web Level Features	GAC	Web.Config	14-RootFeatures	SharePoint Config DB, Objects Table – Solutions	SharePoint Config DB, Objects Table – Features	Web App Content DB, Features Table
Add-SPSolution	Solution Added but Not Deployed	N/A	N/A	N/A	N/A	Yes – Solution Definition Added	N/A	N/A
Install-SPSolution	Deployed to Web App	Installed Feature	Yes – DLLs Added	Yes – Safe Control Entries Added	Yes – Features Added	Yes – Solution Definition Still Exists	Yes – Feature Definition Added	N/A
Enable-SPFeature	Solution Still Deployed	Activated feature to Site/Web	Yes – Still Exists	Yes – Still Exists	Yes – Still Exists	Yes – Solution Definition Still Exists	Yes – Feature Definition Still Exists	YES – Feature Activation Link Added
Disable-SPFeature	Solution Still Deployed	Deactivated feature from Site/Web	Yes – Still Exists	Yes – Still Exists	Yes – Still Exists	Yes – Solution Definition Still Exists	Yes – Feature Definition Still Exists	NO – Feature Activation Link Deleted
UnInstall-SPFeature	Solution Still Deployed	Uninstalled feature	Yes – Still Exists	Yes – Still Exists	Yes – Still Exists	Yes – Solution Definition Still Exists	No – Feature Definition Deleted	N/A
UnInstall-SPSolution	Retracted from Web App	Uninstalled feature	No – DLLs Deleted	No – Safe Control Entries Deleted	No – Features Deleted	Yes – Solution Definition Still Exists	No – Feature Definition Deleted	N/A
Remove-SPSolution	Solution Deleted	N/A	N/A	N/A	N/A	Yes – Solution Definition Deleted	N/A	N/A

Hope this will help you to understand
Many Thanks