Managing and executing serverless function command sets in a messaging service
A serverless function execution system enables fast, efficient and flexible deployment and execution of serverless functions. User commands are received from external messaging systems that cause functions to be executed. A serverless function associated with the user command is determined and the serverless function is executed in an isolation container at a function computation server. A response from the execution of the serverless function is sent to the external messaging system.
1. A method, comprising:
creating a command set, the command set includes one or more commands, associated command definitions, and one or more associated function source code locations;
wherein an external specification file is published at a network accessible location, the external specification file including one or more textual messaging commands associated with each command in the command set along with any parameters that the command accepts;
wherein local system installation of the external specification file causes the command set to be locally defined and visible to a user;
wherein a user-selected command causes a textual messaging command to be sent to an external chat messaging service;
wherein the external chat messaging service sends the textual messaging command to an API endpoint associated with a prefix in the textual messaging command;
receiving the textual messaging command at the API endpoint;
executing a serverless function within an isolation container in response to the received textual messaging command by executing function code using the one or more associated function source code locations;
returning a result of the execution of the serverless function to the external chat messaging service.
2. The method as recited in claim 1 , further comprising:
retrieving function code to execute by referring to an app definition associated with the textual messaging command;
selecting a compute server based on the textual messaging command;
causing the selected compute server to execute the function code.
3. The method as recited in claim 1 , further comprising:
storing a plurality of app definitions;
wherein each app definition includes a mapping of textual messaging command subcommands to function code.
4. The method as recited in claim 1 , wherein an app is associated with a textual messaging command prefix.
5. The method as recited in claim 1 , wherein an app is associated with a textual messaging command prefix, and wherein an app is comprised of one or more subcommands.
6. The method as recited in claim 1 , wherein an app is associated with a textual messaging command prefix, wherein an app is comprised of one or more subcommands, and wherein each of the one or more subcommands is mapped to one or more functions.
7. The method as recited in claim 1 , further comprising:
storing a history of commands that were executed by users and user identities.
8. One or more non-transitory computer-readable storage media, storing one or more sequences of instructions, which when executed by one or more processors cause performance of:
creating a command set, the command set includes one or more commands, associated command definitions, and one or more associated function source code locations;
wherein an external specification file is published at a network accessible location, the external specification file including one or more textual messaging commands associated with each command in the command set along with any parameters that the command accepts;
wherein local system installation of the external specification file causes the command set to be locally defined and visible to a user;
wherein a user-selected command causes a textual messaging command to be sent to an external chat messaging service;
wherein the external chat messaging service sends the textual messaging command to an API endpoint associated with a prefix in the textual messaging command;
receiving the textual messaging command at the API endpoint;
executing a serverless function within an isolation container in response to the received textual messaging command by executing function code using the one or more associated function source code locations;
returning a result of the execution of the serverless function to the external chat messaging service.
9. The one or more non-transitory computer-readable storage media as recited in claim 8 , further comprising:
retrieving function code to execute by referring to an app definition associated with the textual messaging command;
selecting a compute server based on the textual messaging command;
causing the selected compute server to execute the function code.
10. The one or more non-transitory computer-readable storage media as recited in claim 8 , further comprising:
storing a plurality of app definitions;
wherein each app definition includes a mapping of textual messaging command subcommands to function code.
11. The one or more non-transitory computer-readable storage media as recited in claim 8 , wherein an app is associated with a textual messaging command prefix.
12. The one or more non-transitory computer-readable storage media as recited in claim 8 , wherein an app is associated with a textual messaging command prefix, and wherein an app is comprised of one or more subcommands.
13. The one or more non-transitory computer-readable storage media as recited in claim 8 , wherein an app is associated with a textual messaging command prefix, wherein an app is comprised of one or more subcommands, and wherein each of the one or more subcommands is mapped to one or more functions.
14. The one or more non-transitory computer-readable storage media as recited in claim 8 , further comprising:
storing a history of commands that were executed by users and user identities.
15. A system, comprising:
a command set, the command set includes one or more commands, associated command definitions, and one or more associated function source code locations;
wherein an external specification file is published at a network accessible location, the external specification file including one or more textual messaging commands associated with each command in the command set along with any parameters that the command accepts;
wherein local system installation of the external specification file causes the command set to be locally defined and visible to a user;
wherein a user-selected command causes a textual messaging command to be sent to an external chat messaging service;
wherein the external chat messaging service sends the textual messaging command to an API endpoint associated with a prefix in the textual messaging command;
a function computation system, implemented at least partially in hardware, configured to:
receive the textual messaging command at the API endpoint;
execute a serverless function within an isolation container in response to the received textual messaging command by executing function code using the one or more associated function source code locations;
return a result of the execution of the serverless function to the external chat messaging service.
16. The system as recited in claim 15 , further comprising:
retrieving function code to execute by referring to an app definition associated with the textual messaging command;
selecting a compute server based on the textual messaging command;
causing the selected compute server to execute the function code.
17. The system as recited in claim 15 , further comprising:
storing a plurality of app definitions;
wherein each app definition includes a mapping of textual messaging command subcommands to function code.
18. The system as recited in claim 15 , wherein an app is associated with a textual messaging command prefix, and wherein an app is comprised of one or more subcommands.
19. The system as recited in claim 15 , wherein an app is associated with a textual messaging command prefix, wherein an app is comprised of one or more subcommands, and wherein each of the one or more subcommands is mapped to one or more functions.
20. The system as recited in claim 15 , further comprising:
storing a history of commands that were executed by users and user identities.