Reddit mentions of Deploying SharePoint 2016: Best Practices for Installing, Configuring, and Maintaining SharePoint Server 2016

(I'll do it for him... )big fan of this book as the engineer's owners manual for 2016:
https://www.amazon.com/Deploying-SharePoint-2016-Configuring-Maintaining/dp/1484219988

looking for practical aspects of farm management that gets a bit trickier: i'd defer to some of the 2013 books on sp solutions and adoption/governance. ie what is optional somewhat depends on org expectations/needs. also product owner assessment on deprecated tech without clear or replaced by more resource intensive methods (ie infopath, workflow, pub sites, access apps).

let me know if you want more references or have specific questions you are looking for content on.

I just released a book on deploying SharePoint 2016:

https://www.amazon.com/Deploying-SharePoint-2016-Configuring-Maintaining/dp/1484219988/ref=sr_1_1?ie=UTF8&qid=1480399846&sr=8-1&keywords=deploying+sharepoint+2016

/spam

Compared to 2013 wrt Service Apps, not really any difference.

I realize you are working with 2010, but you may be able to use the same approach as from SP2016, so I will reference below, but if not, here are some links to 2010 resources:

http://www.harbar.net/articles/sp2010ups.aspx

https://docs.microsoft.com/en-us/sharepoint/install/create-a-user-profile-service-application

https://social.technet.microsoft.com/wiki/contents/articles/5199.sharepoint-2010-creating-user-profile-service-application-with-solution-to-most-common-issue.aspx

This snippet is from page 341 of Vlad Catrinescu and Trevor Seward's, Deploying SharePoint 2016, which I recommend getting if you will continue working with SharePoint. It's a great resource I keep next to me.

$sa = New-SPProfileServiceApplication -Name "User Profile Service Application" -applicationpool "SharePoint Web Services Default" -ProfileDBName 'Profile_DB_2013' -SocialDBName 'Social_DB_2013' -ProfileSyncDBName 'Sync_DB'

We then need to create Service Application Proxy by using the following cmdlet.

New-SPProfileServiceApplicationProxy -Name "User Profile Service Application Proxy" -ServiceApplication $sa -DefaultProxyGroup

You can purchase their book here:

https://www.amazon.com/Deploying-SharePoint-2016-Configuring-Maintaining/dp/1484219988

Please note, as with anything like this, the names of service applications, application pools, and databases, are all subjective and will need to be determined by your existing environment.

​