Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages wha2tsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Unclear what your goals are. For example, if you have 150 Mbps, why do you wish to restrict traffic to 90 Mbps?
Your goal of insuring traffic is never dropped, might be unrealistic. Some traffic types only use a specific amount of bandwidth, and for those, you can often obtain enough bandwidth to avoid drops, but much other traffic will attempt to consume all possible bandwidth, and for that traffic, sometimes drops are what indicates to the sender all available bandwidth has been used. The best you might accomplish for the latter, is minimal drops to control sender's flow transmission rate to the available bandwidth.
The foregoing paragraph pertains to "typical" QoS features found on a Cisco router. There are 3rd party traffic management applicances that can do even more to regulate traffic.
Regarding whether a policer or shaper is best practice, it depends on what you're trying to accomplish.
