Techniques and Architectures for Providing Continuous Integration (CI) and/or Continuous Delivery (CD) in a Data Lake Environment

1. A system comprising: a constant integration (CI) platform to manage assembly of code for an app, the CI platform to create a container within a shared environment within which the app runs, wherein the container is isolated from other containers and bundles software, libraries and configuration files and can communicate with other containers through defined channels, and the shared environment provides a platform for running the app; the app to write to one or more tables maintained in the shared environment; wherein the CI platform functions to manage assembly of subsequent versions of code for the app, assembly of the subsequent version of code and to deploy the assembled subsequent version of the code to the container, the CI platform further to run integration tests on the deployed subsequent version of the code, and when integration testing is complete, cause the subsequent version of the code to replace the app in the shared environment.

2. The system of claim 1 , wherein the CI platform utilizes one or more scenario specifications to run the integration tests, wherein each of the one or more scenario specifications comprise: metadata that describes a scenario; a list of applications to perform the relevant functionalities of the scenario; and a list of integration tests to verify expected behaviors of the applications in the scenario.

3. The system of claim 1 , wherein the app is deployed to an isolated runtime context based on a namespace corresponding to an application context and properties corresponding to the application context, the application context to be utilized to develop scoped properties.

4. The system of claim 3 , wherein one or more dependent services each having one or more scoped objects function within the scoped properties.

5. The system of claim 3 wherein the application context is utilized to generate the integration tests and to generate a deployment script that utilizes the namespace to limit app scope.

6. The system of claim 1 further comprising: the constant integration (CI) platform to manage assembly of code for a second app to run in the container; the second app to write to the one or more tables maintained in the shared environment; wherein the CI platform functions to manage assembly of subsequent versions of code for the second app, assembly of the subsequent version of code for the second app and to deploy the assembled subsequent version of the code for the second app to the container, the CI platform further to run integration tests on the deployed subsequent version of the code for the second app, and when integration testing is complete, cause the subsequent version of the code for the second app to replace the second app in the shared environment.

7. A non-transitory computer-readable medium having stored thereon instructions that, when executed by one or more processors, are configurable to cause the one or more processors to: manage assembly of code for an app with a constant integration (CI) platform to create a container within a shared environment within which the app runs, wherein the container is isolated from other containers and bundles software, libraries and configuration files and can communicate with other containers through defined channels, and the shared environment provides a platform for running the app; run the app to write to one or more tables maintained in the shared environment; manage assembly, with the CI platform, of subsequent versions of code for the app; manage assembly, with the CI platform, deployment of the assembled subsequent version of the code to the container; run, with the CI platform, integration tests on the deployed subsequent version of the code; and cause, with the CI platform, the subsequent version of the code to replace the app in the shared environment when integration testing is complete.

8. The non-transitory computer-readable medium of claim 7 , wherein the CI platform utilizes one or more scenario specifications to run the integration tests, wherein each of the one or more scenario specifications comprise: metadata that describes a scenario; a list of applications to perform the relevant functionalities of the scenario; and a list of integration tests to verify expected behaviors of the applications in the scenario.

9. The non-transitory computer-readable medium of claim 7 , wherein the app is deployed to an isolated runtime context based on a namespace corresponding to an application context and properties corresponding to the application context, the application context to be utilized to develop scoped properties.

10. The non-transitory computer-readable medium of claim 9 , wherein one or more dependent services each having one or more scoped objects function within the scoped properties.

11. The non-transitory computer-readable medium of claim 9 wherein the application context is utilized to generate the integration tests and to generate a deployment script that utilizes the namespace to limit app scope.

12. The non-transitory computer-readable medium of claim 7 further comprising instructions that, when executed by the one or more processors, are configurable to cause the one or more processors to: manage assembly of code for a second app to run in the container with the constant integration (CI) platform to; run the second app to write to the one or more tables maintained in the shared environment; manage assembly, with the CI platform, of subsequent versions of code for the second app; manage assembly, with the CI platform, deployment of the assembled subsequent version of the code to the container; run, with the CI platform, integration tests on the deployed subsequent version of the code; and cause, with the CI platform, the subsequent version of the code to replace the second app in the shared environment when integration testing is complete.

13. A method comprising: managing assembly of code for an app with a constant integration (CI) platform to create a container within a shared environment within which the app runs, wherein the container is isolated from other containers and bundles software, libraries and configuration files and can communicate with other containers through defined channels, and the shared environment provides a platform for running the app; running the app to write to one or more tables maintained in the shared environment; managing assembly, with the CI platform, of subsequent versions of code for the app; managing assembly, with the CI platform, deployment of the assembled subsequent version of the code to the container; running, with the CI platform, integration tests on the deployed subsequent version of the code; and causing, with the CI platform, the subsequent version of the code to replace the app in the shared environment when integration testing is complete.

14. The method of claim 13 , wherein the CI platform utilizes one or more scenario specifications to run the integration tests, wherein each of the one or more scenario specifications comprise: metadata that describes a scenario; a list of applications to perform the relevant functionalities of the scenario; and a list of integration tests to verify expected behaviors of the applications in the scenario.

15. The method of claim 13 , wherein the app is deployed to an isolated runtime context based on a namespace corresponding to an application context and properties corresponding to the application context, the application context to be utilized to develop scoped properties.

16. The method of claim 15 , wherein one or more dependent services each having one or more scoped objects function within the scoped properties.

17. The method of claim 15 wherein the application context is utilized to generate the integration tests and to generate a deployment script that utilizes the namespace to limit app scope.

18. The method of claim 13 further comprising: managing assembly of code for a second app to run in the container with the constant integration (CI) platform to; running the second app to write to the one or more tables maintained in the shared environment; managing assembly, with the CI platform, of subsequent versions of code for the second app; managing assembly, with the CI platform, deployment of the assembled subsequent version of the code to the container; running, with the CI platform, integration tests on the deployed subsequent version of the code; and causing, with the CI platform, the subsequent version of the code to replace the second app in the shared environment when integration testing is complete.