Secure sidecar container

A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations, comprising:

• reading, by a secure side car (SSC) manager, development artifacts and an application configuration file;
• creating, by the SSC manager, stubs and skeletons for inter-process communication between a main application and one or more SSC library containers, the stubs and skeletons based on SSC configurations specified in the application configuration file, wherein the stubs provide local application programming interfaces (APIs) for remote functionality implemented by libraries in the one or more SSC library containers, and wherein the stubs are configured to marshal API parameters and send the API parameters to the skeletons in the one or more SSC library containers;
• compiling, by the SSC manager, main application code for the main application, wherein compiling comprises linking the created stubs to the main application code;
• creating, by the SSC manager, an application container image for the main application and a SSC image for each of the one or more SSC library containers;
• deploying, by the SSC manager, an application container corresponding to the application container image and a SSC library container corresponding to each SSC image for each of the one or more SSC library containers;
• and
• configuring, by the SSC manager, a service mesh proxy, which controls network access for libraries within each SSC library container and is configured to enable container specific network filtering.

A computer-implemented system, comprising:

• one or more computers;
• and
• one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations, comprising:
• reading, by a secure side car (SSC) manager, development artifacts and an application configuration file;
• creating, by the SSC manager, stubs and skeletons for inter-process communication between a main application and one or more SSC library containers, the stubs and skeletons based on SSC configurations specified in the application configuration file, wherein the stubs provide local application programming interfaces (APIs) for remote functionality implemented by libraries in the one or more SSC library containers, and wherein the stubs are configured to marshal API parameters and send the API parameters to the skeletons in the one or more SSC library containers;
• compiling, by the SSC manager, main application code for the main application, wherein compiling comprises linking the created stubs to the main application code;
• creating, by the SSC manager, an application container image for the main application and a SSC image for each of the one or more SSC library containers;
• deploying, by the SSC manager, an application container corresponding to the application container image and a SSC library container corresponding to each SSC image for each of the one or more SSC library containers;
• and
• configuring, by the SSC manager, a service mesh proxy, which controls network access for libraries within each SSC library container and is configured to enable container specific network filtering.