The biggest problem with any new technology is fitting it into an existing flow with minimal turbulence. The pieces of the flow that are subject to the most friction are:
Where do you go for questions? How will you be able to solve problems that come up?
How stable is the technology? Is it undergoing massive changes? Will going back to code written with this tech one year from now be simple or a nightmare?
How are unit tests written? How testable is code written with this new technology?
Does this new technology affect the build process at all?
Do your deployments change? What metrics need to be tracked in order to measure the impact of the new technology?
It’s important to run through at least these checkpoints in order to get a high-level overview of the problems you might face, although it might be tempting to charge forward once you’ve gotten past the first hurdle because that’s usually the primary focus of technology marketing.