Abstract: A method of providing Application Programming Interface (API) functions for registered service endpoints in container environments may include receiving, at an API registry, a request from a second service to use a first service in a container environment, where the API registry may list one or more API functions that call the first service. The method may also include generating, by the API registry, a client library for the second service that includes the one or more API functions to execute calls from the second service to the first service in the container environment.

Abstract: A method of customizing deployment and operation of services in container environments may include receiving, at an API registry, a property for a service that is or will be encapsulated in a container that is or will be deployed in a container environment. The method may also include determining whether the property for the service affects the deployment of the service to the container environment, and in response to a determination that the property affects the deployment of the service, deploying the service based at least in part on the property. The method may additionally include determining whether the property for the service affects the generation of a client library that calls the service in the container environment, and in response to a determination that the property affects the generation of the client library, generating the client library based at least in part on the property.

Abstract: A method of providing Application Programming Interface (API) functions for registered service endpoints in container environments may include receiving, at an API registry, a request from a second service to use a first service in a container environment, where the API registry may list one or more API functions that call the first service. The method may also include generating, by the API registry, a client library for the second service that includes the one or more API functions to execute calls from the second service to the first service in the container environment.

Abstract: A method of providing Application Programming Interface (API) functions for registered service endpoints in container environments includes receiving, at an API registry, a request from a second service to use a first service in a container environment; providing an API function to the second service, where the API function is included as part of the second service to execute calls from the second service to the first service in the container environment; receiving a request from the API function for an endpoint of the first service; and providing the endpoint of the first service such that the API function in the second service can execute a call to the endpoint of the first service in the container environment.

Abstract: A method may include receiving a request for a service at a container environment. The container environment may include a service mesh and a plurality of services encapsulated in a plurality of containers. The service may be encapsulated in first one or more containers. The method may also include determining that the request should be routed to a debug instance of the service; and instantiating the debug instance of the service. The debug instance may be encapsulated in second one or more containers and may include code implementing the service and one or more debugging utilities. The method may additionally include routing, by the service mesh, the request to the debug instance.

Abstract: A method may include deploying a plurality of container pods to a plurality of container nodes in a container environment. Each of the plurality of container pods may include one or more services. Each of the plurality of container nodes may include one or more container pods. The plurality of container pods may be deployed to the plurality of container nodes based on initial characterizations of usage factors for each of the plurality of container pods. The method may also include monitoring actual usage factors for each of the plurality of container pods after deployment to the plurality of container nodes; identifying one or more container pods in the plurality of container pods that deviate from their initial characterizations of usage factors; and redistributing the one or more container pods throughout the plurality of container nodes based on the actual usage factors.

Abstract: A method of providing Application Programming Interface (API) functions for registered service endpoints in container environments includes receiving, at an API registry, a request from a second service to use a first service in a container environment; providing an API function to the second service, where the API function is included as part of the second service to execute calls from the second service to the first service in the container environment; receiving a request from the API function for an endpoint of the first service; and providing the endpoint of the first service such that the API function in the second service can execute a call to the endpoint of the first service in the container environment.

Abstract: A method of customizing deployment and operation of services in container environments may include receiving, at an API registry, a property for a service that is or will be encapsulated in a container that is or will be deployed in a container environment. The method may also include determining whether the property for the service affects the deployment of the service to the container environment, and in response to a determination that the property affects the deployment of the service, deploying the service based at least in part on the property. The method may additionally include determining whether the property for the service affects the generation of a client library that calls the service in the container environment, and in response to a determination that the property affects the generation of the client library, generating the client library based at least in part on the property.

Abstract: A method of providing Application Programming Interface (API) functions for registered service endpoints in container environments may include receiving, at an API registry, an API definition that may include an endpoint of a first service that is encapsulated in a container that is deployed in a container environment and one or more API functions. The method may also include creating, by the API registry, a binding between the one or more API functions and the endpoint of the service; receiving, by the API registry, a request from a second service to use the first service; and providing, by the API registry, the one or more API functions to the second service.

Abstract: A method of customizing deployment and operation of services in container environments may include receiving, at an API registry, a property for a service that is or will be encapsulated in a container that is or will be deployed in a container environment. The method may also include determining whether the property for the service affects the deployment of the service to the container environment, and in response to a determination that the property affects the deployment of the service, deploying the service based at least in part on the property. The method may additionally include determining whether the property for the service affects the generation of a client library that calls the service in the container environment, and in response to a determination that the property affects the generation of the client library, generating the client library based at least in part on the property.

Abstract: A method of customizing deployment and operation of services in container environments may include receiving, at an API registry, a property for a service that is or will be encapsulated in a container that is or will be deployed in a container environment. The method may also include determining whether the property for the service affects the deployment of the service to the container environment, and in response to a determination that the property affects the deployment of the service, deploying the service based at least in part on the property. The method may additionally include determining whether the property for the service affects the generation of a client library that calls the service in the container environment, and in response to a determination that the property affects the generation of the client library, generating the client library based at least in part on the property.

Abstract: A method may include receiving a request for a service at a container environment. The container environment may include a service mesh and a plurality of services encapsulated in a plurality of containers. The service may be encapsulated in first one or more containers. The method may also include determining that the request should be routed to a debug instance of the service; and instantiating the debug instance of the service. The debug instance may be encapsulated in second one or more containers and may include code implementing the service and one or more debugging utilities. The method may additionally include routing, by the service mesh, the request to the debug instance.

Abstract: A method of providing Application Programming Interface (API) functions for registered service endpoints in container environments may include receiving, at an API registry, an API definition that may include an endpoint of a first service that is encapsulated in a container that is deployed in a container environment and one or more API functions. The method may also include creating, by the API registry, a binding between the one or more API functions and the endpoint of the service; receiving, by the API registry, a request from a second service to use the first service; and providing, by the API registry, the one or more API functions to the second service.

Abstract: A method of distributing microservice containers for a service across a plurality of computing environments may include receiving a service that is built from a plurality of containerized microservices to be deployed in a container platform. The container platform may include a plurality of computing environments. The method may also include receiving a deployment criteria for deploying the service in the container platform; accessing characteristics of the plurality of computing environments; and deploying the plurality of containerized micro services across the plurality of computing environments based on the deployment criteria and the characteristics of the plurality of computing environments.

Abstract: A method may include deploying a plurality of container pods to a plurality of container nodes in a container environment. Each of the plurality of container pods may include one or more services. Each of the plurality of container nodes may include one or more container pods. The plurality of container pods may be deployed to the plurality of container nodes based on initial characterizations of usage factors for each of the plurality of container pods. The method may also include monitoring actual usage factors for each of the plurality of container pods after deployment to the plurality of container nodes; identifying one or more container pods in the plurality of container pods that deviate from their initial characterizations of usage factors; and redistributing the one or more container pods throughout the plurality of container nodes based on the actual usage factors.

Abstract: Various technologies and techniques are disclosed for providing optimized garbage collection. A garbage collector is provided for managing a garbage collection process. An optimized garbage collection feature is provided that allows the garbage collection process to be suggested. When the optimized garbage collection feature is invoked at a particular moment, the system determines if collection is appropriate at the particular moment. If collection is determined to be appropriate at the particular moment, then the system performs the garbage collection process. If collection is determined to not be appropriate at the particular moment, then the system delays garbage collection until an appropriate time. A low latency mode can be used to automatically ensure that the garbage collection process starts sooner than it would in a normal mode. The latency mode in use can be changed at different points in time during the garbage collection process.

Abstract: Scalable object model design is described. In an embodiment, one or more objects corresponding to a form are instantiated in response to a request for the form from a first client device, and an events manager is instantiated through which the one or more objects register to process data manipulation events associated with the form. Data specific to the first client device is processed with the one or more objects that correspond to the form via a first processor thread. An additional request from a second client device is received and additional data specific to the second client device is processed with the one or more objects that correspond to the form via a second processor thread. The one or more objects are shared by the first client device and the second client device to process the data manipulation events associated with the form.

Abstract: Various technologies and techniques are disclosed for providing optimized garbage collection. A garbage collector is provided for managing a garbage collection process. An optimized garbage collection feature is provided that allows the garbage collection process to be suggested. When the optimized garbage collection feature is invoked at a particular moment, the system determines if collection is appropriate at the particular moment. If collection is determined to be appropriate at the particular moment, then the system performs the garbage collection process. If collection is determined to not be appropriate at the particular moment, then the system delays garbage collection until an appropriate time. A low latency mode can be used to automatically ensure that the garbage collection process starts sooner than it would in a normal mode. The latency mode in use can be changed at different points in time during the garbage collection process.

Abstract: Scalable object model design is described. In an embodiment, one or more objects corresponding to a form are instantiated in response to a request for the form from a first client device, and an events manager is instantiated through which the one or more objects register to process data manipulation events associated with the form. Data specific to the first client device is processed with the one or more objects that correspond to the form via a first processor thread. An additional request from a second client device is received and additional data specific to the second client device is processed with the one or more objects that correspond to the form via a second processor thread. The one or more objects are shared by the first client device and the second client device to process the data manipulation events associated with the form.

Abstract: The invention relates to a document analysis method to detect BW/color areas comprising the following steps: getting an input image data to be split in elementary information; analysing the input data to get the colorfulness of each elementary information; creating a first and a second output layers corresponding to the BW and color elementary information respectively; applying a first set of atomic operations to the BW layer and a second different set of atomic operations to the color layer; and combining the BW and color layers in order to obtain a desired format for the output data. The invention also relates to a scanning device to acquire documents including an input that receives an input image data, and is connected to a layer creator component, which in turn outputs a first and a second layer, such layers having different data compression rate. Finally, the invention relates to a method for acquiring a document based on the analysis of the content of the document itself.