Container Onboarding in Distributed Cloud Environment

A method for onboarding containers in a distributed cloud environment, the method comprising:

• storing, by a database, a plurality of container configurations, each container configuration including a container identifier, a validation requirement, a list of microservices, a data block mapping, an onboarding decision, a resource allocation, a data classification, and a repository mapping;
• loading, by an admin system, the plurality of container configurations from the database into an admin cache at system startup;
• loading, by a plurality of microservices, the plurality of container configurations from the database into a microservice cache at system startup;
• generating, by the admin system, a plurality of JSON templates, each JSON template corresponding to a respective container configuration and defining a user interface layout and operational criteria;
• synchronizing, by a scheduler, the admin cache and the microservice cache with the database every 24 hours to update the plurality of container configurations;
• updating, by the plurality of microservices, repository connections dynamically based on the synchronized container configurations;
• receiving, by the admin system, a new container configuration from an onboarding team;
• inserting, by the admin system, the new container configuration into the database;
• caching, by the admin system, the new container configuration in the admin cache;
• caching, by the plurality of microservices, the new container configuration in the microservice cache;
• generating, by the admin system, a new JSON template for the new container configuration;
• processing, by the admin system, a user request for a container by validating the request against the container configuration and selecting a microservice from the list of microservices;
• executing, by the selected microservice, an operation based on the repository mapping in the container configuration;
• rendering, by the admin system, a result of the operation using the user interface layout from the corresponding JSON template;
• validating, by the admin system, the user request by checking the data classification in the container configuration against a user role;
• restricting, by the admin system, access to the container if the data classification indicates confidential data and the user role lacks authorization;
• building, by the selected microservice, a query for the operation based on input data from the user request;
• executing, by the selected microservice, the query against a repository specified in the repository mapping to retrieve or update data;
• refreshing, by the scheduler, the admin cache and the microservice cache incrementally by synchronizing only updated fields in the container configurations;
• adjusting, by the admin system, the user interface layout dynamically based on the data block mapping in the container configuration;
• routing, by the selected microservice, the operation to a secondary repository if a primary repository specified in the repository mapping is unavailable;
• simulating, by the admin system, the new container configuration prior to inserting it into the database to preview its impact;
• logging, by the admin system, synchronization events and onboarding actions to maintain an audit trail;
• assigning, by the admin system, a target cloud provider to the new container configuration for onboarding across multi-cloud environments;
• monitoring, by the admin system, performance metrics of the container after onboarding to refine future configurations;
• and
• versioning, by the database, the plurality of container configurations to enable reversion to previous settings.

A system for onboarding containers in a distributed cloud environment, the system comprising:

• a database configured to store a plurality of container configurations, each container configuration including a container identifier that uniquely identifies a container, a validation requirement that specifies whether validation is needed, a list of microservices that identifies associated microservices, a data block mapping that defines data storage locations, an onboarding decision that determines cloud integration, a resource allocation that assigns memory and CPU resources, a data classification that categorizes data type, and a repository mapping that links operations to data repositories;
• an admin system configured to load the plurality of container configurations from the database into an admin cache at system startup, the admin cache storing the configurations for rapid access;
• a plurality of microservices configured to load the plurality of container configurations from the database into a microservice cache at system startup, the microservice cache enabling microservice operations;
• the admin system further configured to generate a plurality of JSON templates, each JSON template corresponding to a respective container configuration and defining a user interface layout that presents operational options and operational criteria that specify supported actions;
• a scheduler configured to synchronize the admin cache and the microservice cache with the database every 24 hours, the synchronization updating the plurality of container configurations to reflect changes;
• the plurality of microservices further configured to update repository connections dynamically, the dynamic updating adjusting data access based on the synchronized container configurations;
• the admin system further configured to receive a new container configuration from an onboarding team, the new container configuration specifying parameters for a new container;
• the admin system further configured to insert the new container configuration into the database, the insertion making the new configuration persistent;
• the admin system further configured to cache the new container configuration in the admin cache, the caching enabling immediate admin access;
• the plurality of microservices further configured to cache the new container configuration in the microservice cache, the caching enabling immediate microservice access;
• the admin system further configured to generate a new JSON template for the new container configuration, the new JSON template defining the new container's interface and operations;
• the admin system further configured to process a user request for a container by validating the request against the container configuration, the validation ensuring compliance, and selecting a microservice from the list of microservices, the selection identifying the operation executor;
• the selected microservice configured to execute an operation based on the repository mapping in the container configuration, the execution performing data retrieval or modification;
• and
• the admin system further configured to render a result of the operation using the user interface layout from the corresponding JSON template, the rendering presenting the outcome to the user.