Extending automation with Java and Salesforce Functions

So far Heroku has been used to build web and API experiences coded in Node.js and Postgres and run your code constantly through the use of Heroku Dynos. The interactions with those experiences come from external integrations, typically where response times are important. Salesforce Functions, however, offers much of the flexibility of Heroku Dynos with respect to support for additional programming languages, such as Java, Node.js, and Python as well as offering greater elastic scale for more intensive workloads that require more memory, CPU, and asynchronous scale compared to Apex. Functions also have no callout or asynchronous limits when compared to Apex.

In contrast to Heroku Dynos, Salesforce Functions run only when needed, so only use up compute resources when needed; a downside of this is there can sometimes be a startup cost if a function has not been invoked recently. One big difference is that they have tighter integration...