Abstract: Described embodiments provide systems and methods for recording metadata about a microservice for requests to the microservice. A device configured as a proxy to one or more microservices of a service can receive a registration request to register a microservice of the one or more microservices with the device. Metadata can be received during registration of the microservice with the device. The metadata can identify an identifier of the microservice, a deployment version of the microservice and a region of deployment of the microservice. The device can store the metadata in association with the microservice and record the metadata of the microservice registered with the device in association with a plurality of requests. The device can identify, via a user interface and the metadata recorded to the log, a change in operation of the microservice in connection with one of the deployment version or the region of the microservice.

Abstract: Described embodiments provide systems and methods for identifying a context of an endpoint accessing a plurality of microservices is provided. A device intermediary to a plurality of endpoints and a plurality of microservices can receive a plurality of calls to one or more of the plurality of microservices originating from the plurality of endpoints. The device can identify a context for each of the endpoints. The context can include one of a type of device or a type of application. The device can identify, for each unique context, one or more microservices of the accessed by the plurality of endpoints having that unique context. A service graph can be generated to identify the one or more microservices of the plurality of microservices accessed by the plurality of endpoints having that at least one unique context.

Abstract: Described herein are systems and methods for transparent resiliency to multiple data centers. The systems and methods depicted determine if an application programming interface (API) call is idempotent. If the API call is idempotent, the calls can be concurrently forwarded to multiple datacenters. If the API call is not idempotent, the calls can be sent to each of a multiple datacenters in turn until a response is received or timeout occurs. Automatically providing multi-region calls in synchrony provides a faster response time during data center or regional failures. Automatically providing multi-region calls in synchrony at the appliance server side, moves the logic out of the client and into a transparent and centrally managed service.

Abstract: Described embodiments provide systems and methods for using a call chain to identify dependencies among a plurality of microservices. A device intermediary to a plurality of microservices can receive a first request to access a first microservice. The processing of the first request can cause the first microservice to communicate a second request to a second microservice. A first unique identifier can be generated for the first request to the first microservice and the device can establish a call chain for identifying a plurality of requests to a first microservice through a last microservice of the plurality of microservices accessed responsive to the first request. The device can forward the first request including the call chain to the first microservice and the second request including the call chain to the second microservice. The device can identify, via the call chain, that the first microservice depends on the second microservice.

Abstract: Described embodiments provide systems and methods for identifying a context of an endpoint accessing a plurality of microservices is provided. A device intermediary to a plurality of endpoints and a plurality of microservices can receive a plurality of calls to one or more of the plurality of microservices originating from the plurality of endpoints. The device can identify a context for each of the endpoints. The context can include one of a type of device or a type of application. The device can identify, for each unique context, one or more microservices of the accessed by the plurality of endpoints having that unique context. A service graph can be generated to identify the one or more microservices of the plurality of microservices accessed by the plurality of endpoints having that at least one unique context.

Abstract: Described herein are systems and methods for transparent resiliency to multiple data centers. The systems and methods depicted determine if an application programming interface (API) call is idempotent. If the API call is idempotent, the calls can be concurrently forwarded to multiple datacenters. If the API call is not idempotent, the calls can be sent to each of a multiple datacenters in turn until a response is received or timeout occurs. Automatically providing multi-region calls in synchrony provides a faster response time during data center or regional failures. Automatically providing multi-region calls in synchrony at the appliance server side, moves the logic out of the client and into a transparent and centrally managed service. This can allow business logic to focus on the core logic and not on logic to retry requests or manage the multi-regional aspect of a dependent service.

Abstract: Described embodiments provide systems and methods for using a call chain to identify dependencies among a plurality of microservices. A device intermediary to a plurality of microservices can receive a first request to access a first microservice. The processing of the first request can cause the first microservice to communicate a second request to a second microservice. A first unique identifier can be generated for the first request to the first microservice and the device can establish a call chain for identifying a plurality of requests to a first microservice through a last microservice of the plurality of microservices accessed responsive to the first request. The device can forward the first request including the call chain to the first microservice and the second request including the call chain to the second microservice. The device can identify, via the call chain, that the first microservice depends on the second microservice.

Abstract: Described embodiments provide systems and methods for monitoring service level compliance of an entity's use of application programming interfaces of a service. A device can identify a service level definition for a service used by an entity. The service can include a plurality of application programming interfaces (APIs). The service level definition can include one or more thresholds regarding use by the entity of the plurality of APIs. The device can receive, from one or more devices of the entity, a plurality of requests to access one or more APIs of the plurality of APIs of the service. The device can record information about the entity's use of the plurality of APIs of the service. The device can compare the recorded information to the one or more thresholds of the service level definition.

Abstract: Described embodiments provide systems and methods for validating a microservice. A device intermediary to a plurality of microservices may identify a synthetic error and a first criteria for implementing the synthetic error to validate a first microservice of the plurality of microservices. The device may determine that the first criteria for implementing the synthetic error has been met. The device may receive a request from the first microservice to access a second microservice of the plurality of microservices. Responsive to the determination, the device may transmit, to the first microservice, a response on behalf of the second microservice, the response implementing the synthetic error. The device may validate that the first microservice one of handled or did not handle the synthetic error.

Abstract: Described embodiments provide systems and methods for executing a plurality of validation tests to validate a plurality of microservices of one or more services. A device intermediary to a plurality of microservices of one or more services identifies a plurality of validation tests, each of the validation tests configured with a timeline, a target microservice and one of a synthetic error or a latency to implement to validate the target microservice. The device executes a first validation test of the plurality of validation tests to implement, over a first timeline, one of a first synthetic error or a first latency in responding to a first target microservice of the plurality of microservices. The device executes a second validation test of the plurality of validation tests to implement, over a second timeline, one of a second synthetic error or a second latency in responding to a second target microservice of the plurality of microservices.

Abstract: Described herein are systems and methods for transparent resiliency to multiple data centers. The systems and methods depicted determine if an application programming interface (API) call is idempotent. If the API call is idempotent, the calls can be concurrently forwarded to multiple datacenters. If the API call is not idempotent, the calls can be sent to each of a multiple datacenters in turn until a response is received or timeout occurs. Automatically providing multi-region calls in synchrony provides a faster response time during data center or regional failures. Automatically providing multi-region calls in synchrony at the appliance server side, moves the logic out of the client and into a transparent and centrally managed service.

Abstract: Described embodiments provide systems and methods for identifying a context of an endpoint accessing a plurality of microservices is provided. A device intermediary to a plurality of endpoints and a plurality of microservices can receive a plurality of calls to one or more of the plurality of microservices originating from the plurality of endpoints. The device can identify a context for each of the endpoints. The context can include one of a type of device or a type of application. The device can identify, for each unique context, one or more microservices of the accessed by the plurality of endpoints having that unique context. A service graph can be generated to identify the one or more microservices of the plurality of microservices accessed by the plurality of endpoints having that at least one unique context.

Abstract: Described embodiments provide systems and methods for determining a health of a service via execution of validation tests on microservices of the service. A device intermediary to a plurality of microservices of one or more services executes a plurality of validation tests, each of the plurality of validation tests configured with a timeline, a target microservice and one of a synthetic error or a latency to implement to validate the target microservice. The device determines, responsive to execution of the plurality of validation tests, one or more disruptions in one or more of the plurality of microservices caused by one of the synthetic error or the latency of one or more of the plurality of validation tests. The device identifies, via a user interface and during at least a portion of execution of one or more of the plurality of validation tests, a health of the one or more services and an indication of the one or more disruptions.

Abstract: Described embodiments provide systems and methods of using an error budget for monitoring performance of a service level of a service is provided. A device intermediary to a plurality of requestors and a plurality of services can identify an error budget for a service level of a service. The error budget can include an amount for which the service is allowed to fall below the service level. The device can monitor, via requests from the requestors to the service, performance of the service with respect to the service level. The device can determine one or more instances for which the service falls below the service level and allocate one or more amounts from the error budget. The device can display the usage of the error budget for the service in association with the service level.

Abstract: Described embodiments provide systems and methods for recording metadata about a microservice for requests to the microservice. A device configured as a proxy to one or more microservices of a service can receive a registration request to register a microservice of the one or more microservices with the device. Metadata can be received during registration of the microservice with the device. The metadata can identify an identifier of the microservice, a deployment version of the microservice and a region of deployment of the microservice. The device can store the metadata in association with the microservice and record the metadata of the microservice registered with the device in association with a plurality of requests. The device can identify, via a user interface and the metadata recorded to the log, a change in operation of the microservice in connection with one of the deployment version or the region of the microservice.

Abstract: The present invention basically relates to an arrangement of individual seats intended to be installed in an aeroplane cabin comprising at least one module of two seats disposed opposite one another, said module having a longitudinal elongation direction, characterized in that said arrangement further comprises: a console disposed between the two seats of the module; a screen connected to each seat, each screen being mounted on a screen support; the screen supports being movable between a stowed position and a deployed operating position, in which the screen supports are positioned substantially edge-to-edge and form a partition wall between the two seats located opposite one another.

Abstract: The present invention essentially relates to an arrangement of individual seats intended to be installed in a cabin of an aeroplane, the arrangement of seats comprising at least one assembly of two seats turned towards the interior in the direction of the longitudinal axis of the arrangement, characterised in that: an end assembly comprises a first seat and a second seat, each seat being convertible between a sitting position and a recumbent position in which the seat defines a bed surface, and an intermediate element having a surface, referred to as the intermediate surface, located in the same plane as the bed surfaces of the first seat and of the second seat, such that the bed surfaces of the first seat and of the second seat as well as the intermediate surface form a common bed surface.

Abstract: An arrangement of individual seats for installation in an aeroplane cabin having a first set of two seats and a second set of two seats, each seat having an axis and being convertible between a sitting position and an extended position, said arrangement having a longitudinal axis. The arrangement also includes (i) a first central console having a first foot area and a second foot area open in two opposite directions relative to each other and respectively associated with the first seat of the first set and the first seat of the second set and (ii) a second central console having a first foot area and a second foot area open in two opposite directions relative to each other and respectively associated with the second seat of the first set and the second seat of the second set.

Abstract: A mesoporous material is derived from a polysaccharide by thermally assisted partial carbonisation after expansion. The polysaccharide is an acid containing polysaccharide or mixture of polysaccharides.

Abstract: A mesoporous material is derived from a polysaccharide by thermally assisted partial carbonisation after expansion. The polysaccharide is an acid containing polysaccharide or mixture of polysaccharides.