Example if I want to send message to some message pump, I want integration come from same developers who make that message pump, or from Delphi and not adding dependency some other party.
Same thing with databases or many protocols.
Understand how responsibilities are formed:
-High level components. Like memory caches, message pumps, load balancers, logging systems, mail, authentication, databases, PBX... They do heavy work, they often offer integrations set of languages
-Framework. Framework set some of coding conventions to shared with development team and
handle integrations all components for your language. Most important features are maintenance and documentation.
-Language. You use it to model your business domain, solving your/shareholder/client etc problem. You add some adapter to interfacing it with infrastructure. Most important features are formal grammar and different languages are used in different domains because language also cross cut to framework and integrations.
That is worst idea ever to have plenty of extra dependencies on some plugins/components. That kind of trash can't be accepted to serious work, never. Because, everything is changing all the time and we want to avoid maintenance work, not increasing it with some extra commercial components. Also need to consider for external audit when there is safety requirements.
I'm just planning new software and essential integrations are for RabbitMQ 4.x, FreeSWITCH, AWS and Google Cloud. Also I need integration for configuration UI using HTTPS and external integration for MQTT, HTTPS and email.
That limits language options for Java, C#, Go, Python, JavaScript/Typescript. From those options Go is the most suitable for this project.