Abstract: A software service can be dynamically switched between a stateless mode and a stateful mode in accordance with some examples described herein. For example, a system can detect an event associated with transitioning a software service from a stateless mode to a stateful mode. In response to detecting the event, the system can execute an allocation module for causing a persistent volume to be allocated to the software service. In response to detecting the event, the system can also execute a switching module for causing the software service to switch from (i) the stateless mode in which state information is not stored in the persistent volume to (ii) the stateful mode in which the state information is stored in the persistent volume.

Abstract: Aspects of the present disclosure relate to fleetwide serverless functional safety protection for hybrid cloud interoperability. More specifically, a processing device receives, from a requesting entity, a message comprising an indication of a resource of a vehicle and an indication of the requesting entity. The processing device determines, based on the message and a set of safety rules for a set of resources of the vehicle, a safety level of the resource. The processing device exposes, to the requesting entity, a serverless function corresponding to the resource of the vehicle from amongst a plurality of serverless functions based on the safety level.

Abstract: A software service can be dynamically switched between a stateless mode and a stateful mode in accordance with some examples described herein. For example, a system can detect an event associated with transitioning a software service from a stateless mode to a stateful mode. In response to detecting the event, the system can execute an allocation module for causing a persistent volume to be allocated to the software service. In response to detecting the event, the system can also execute a switching module for causing the software service to switch from (i) the stateless mode in which state information is not stored in the persistent volume to (ii) the stateful mode in which the state information is stored in the persistent volume.

Abstract: A software service can be dynamically switched between a stateless mode and a stateful mode in accordance with some examples described herein. For example, a system can detect an event associated with transitioning a software service from a stateless mode to a stateful mode. In response to detecting the event, the system can execute an allocation module for causing a persistent volume to be allocated to the software service. In response to detecting the event, the system can also execute a switching module for causing the software service to switch from (i) the stateless mode in which state information is not stored in the persistent volume to (ii) the stateful mode in which the state information is stored in the persistent volume.

Abstract: A fraud prevention exchange system is provided for gathering transaction data for centralized review. The system comprises a database for storing transaction data received from participating lenders and a data retrieval and processing engine for receiving transaction data including a first transaction status code and one or more transaction attributes for a pending transaction from a first participating lender; storing the first transaction status code in association with the transaction attribute(s) in the database; receiving a transaction verification request comprising at least one of the transaction attribute(s) from a second, different participating lender; determining one or more risk alerts for the at least one of the transaction attribute(s) based on the first transaction status code and one or more prior transaction status codes previously stored in the database in association with said attribute; and transmit said risk alert(s) to the second participating lender.

Abstract: A fraud prevention exchange system is provided for gathering transaction data for centralized review. The system comprises a database for storing transaction data received from participating lenders and a data retrieval and processing engine for receiving transaction data including a first transaction status code and one or more transaction attributes for a pending transaction from a first participating lender; storing the first transaction status code in association with the transaction attribute(s) in the database; receiving a transaction verification request comprising at least one of the transaction attribute(s) from a second, different participating lender; determining one or more risk alerts for the at least one of the transaction attribute(s) based on the first transaction status code and one or more prior transaction status codes previously stored in the database in association with said attribute; and transmit said risk alert(s) to the second participating lender.

Abstract: The use of a compound of formula (I): in a method of manufacturing a medicament for the treatment or prophylaxis of a condition wherein inhibition of carboxypeptidase U is beneficial; specified compounds of formula (I) and compositions comprising a compound of formula (I) and a pharmaceutically acceptable adjuvant, diluent or carrier.

Abstract: A network-based method and system for distributing data, such as service data for various types of service processes and models, including software applications, specifications, user's manuals, or parameters, etc, over a data transmission network. A remote service provider maintains a database of the data. The database is updated frequently. The remote service provider maintains a website for authorized users to access the data. Authorized users can access and download desired data by connecting to the remote service provider via the data transmission network. Certain approaches are used to verify a user's identity. In one aspect, a combination of a product code that is specific to a system and a license/activation code that is generated based on the product code is verified. Unless a proper combination exists, the downloaded data cannot be properly accessed. The remote service provider also allows users to purchase a license to access the data online.

Abstract: A network-based method and system for distributing data, such as service data for various types of service processes and models, including software applications, specifications, user's manuals, or parameters, etc, over a data transmission network. A remote service provider maintains a database of the data. The database is updated frequently. The remote service provider maintains a website for authorized users to access the data. Authorized users can access and download desired data by connecting to the remote service provider via the data transmission network. Certain approaches are used to verify a user's identity. In one aspect, a combination of a product code that is specific to a system and a license/activation code that is generated based on the product code is verified. Unless a proper combination exists, the downloaded data cannot be properly accessed. The remote service provider also allows users to purchase a license to access the data online.