Abstract: Systems and methods of rate limiting are disclosed herein. In some example embodiments, a rate limiter service receives a request from an online application to access an online resource, and the rate limiter service transmits an indication of the request to a back end system, and an enforcement decision corresponding to the online resource is received from the back end system, with the enforcement decision comprising an instruction to either permit or deny access to the online resource, and the receiving of the enforcement decision from the back end system being performed asynchronously with the receiving of the request and the transmitting of the indication. In some example embodiments, the enforcement decision received from the back end system is stored, the stored enforcement decision is accessed in response to the receiving of the request, and the request is responded to using the accessed enforcement decision.

Abstract: Systems and methods of rate limiting are disclosed herein. In some example embodiments, a rate limiter service receives a request from an online application to access an online resource, and the rate limiter service transmits an indication of the request to a back end system, and an enforcement decision corresponding to the online resource is received from the back end system, with the enforcement decision comprising an instruction to either permit or deny access to the online resource, and the receiving of the enforcement decision from the back end system being performed asynchronously with the receiving of the request and the transmitting of the indication. In some example embodiments, the enforcement decision received from the back end system is stored, the stored enforcement decision is accessed in response to the receiving of the request, and the request is responded to using the accessed enforcement decision.

Abstract: Systems and methods of rate limiting are disclosed herein. In some example embodiments, a rate limiter service receives a request from an online application to access an online resource, and the rate limiter service transmits an indication of the request to a back end system, and an enforcement decision corresponding to the online resource is received from the back end system, with the enforcement decision comprising an instruction to either permit or deny access to the online resource, and the receiving of the enforcement decision from the back end system being performed asynchronously with the receiving of the request and the transmitting of the indication. In some example embodiments, the enforcement decision received from the back end system is stored, the stored enforcement decision is accessed in response to the receiving of the request, and the request is responded to using the accessed enforcement decision.

Abstract: Systems and methods of rate limiting are disclosed herein. In some example embodiments, a rate limiter service receives a request from an online application to access an online resource, and the rate limiter service transmits an indication of the request to a back end system, and an enforcement decision corresponding to the online resource is received from the back end system, with the enforcement decision comprising an instruction to either permit or deny access to the online resource, and the receiving of the enforcement decision from the back end system being performed asynchronously with the receiving of the request and the transmitting of the indication. In some example embodiments, the enforcement decision received from the back end system is stored, the stored enforcement decision is accessed in response to the receiving of the request, and the request is responded to using the accessed enforcement decision.

Abstract: Systems and methods of rate limiting are disclosed herein. In some example embodiments, a rate limiter service receives a request from an online application to access an online resource, and the rate limiter service transmits an indication of the request to a back end system, and an enforcement decision corresponding to the online resource is received from the back end system, with the enforcement decision comprising an instruction to either permit or deny access to the online resource, and the receiving of the enforcement decision from the back end system being performed asynchronously with the receiving of the request and the transmitting of the indication. In some example embodiments, the enforcement decision received from the back end system is stored, the stored enforcement decision is accessed in response to the receiving of the request, and the request is responded to using the accessed enforcement decision.

Abstract: Systems and methods of rate limiting are disclosed herein. In some example embodiments, a rate limiter service receives a request from an online application to access an online resource, and the rate limiter service transmits an indication of the request to a back end system, and an enforcement decision corresponding to the online resource is received from the back end system, with the enforcement decision comprising an instruction to either permit or deny access to the online resource, and the receiving of the enforcement decision from the back end system being performed asynchronously with the receiving of the request and the transmitting of the indication. In some example embodiments, the enforcement decision received from the back end system is stored, the stored enforcement decision is accessed in response to the receiving of the request, and the request is responded to using the accessed enforcement decision.

Abstract: A computer-implemented system and method for processing messages using native data serialization/deserialization without any transformation, in a service-oriented pipeline architecture is disclosed. The method in an example embodiment that includes serializing or deserializing the request/response message directly into the format (specific on-the-wire data format or a java object) the recipient expects (either a service implementation or a service consumer or the framework), without first converting into an intermediate format. This provides an efficient mechanism for the same service implementation to be accessed by exchanging messages using different data formats.

Abstract: A computer-implemented system and method for creating, managing, and reusing schema type definitions in SOA services, grouped in the form of libraries are disclosed. The method in an example embodiment includes: grouping a plurality of Extensible Mark-up Language (XML) schema (XSD) types, each XSD type defined in an individual XSD file; using a processor to bundle the plurality of individual XSD types into a type library, the type library including a type information file to register the individual XSD types in the type library, the type library further including a type dependencies file to register dependencies between the individual XSD types in the same or different type library; importing types from a different type library, when defining derived types or aggregated types; generating Java artifacts from the XSD types; and associating the Java artifacts with corresponding XSD types in the type information file of the type library.

Abstract: A computer-implemented system and method for processing messages using native data serialization/deserialization without any transformation, in a service-oriented pipeline architecture is disclosed. The method in an example embodiment that includes serializing or deserializing the request/response message directly into the format (specific on-the-wire data format or a java object) the recipient expects (either a service implementation or a service consumer or the framework), without first converting into an intermediate format. This provides an efficient mechanism for the same service implementation to be accessed by exchanging messages using different data formats.

Abstract: A computer-implemented system and method for processing messages using native data serialization/deserialization without any transformation, in a service-oriented pipeline architecture is disclosed. The method in an example embodiment that includes serializing or deserializing the request/response message directly into the format (specific on-the-wire data format or a java object) the recipient expects (either a service implementation or a service consumer or the framework), without first converting into an intermediate format. This provides an efficient mechanism for the same service implementation to be accessed by exchanging messages using different data formats.

Abstract: A computer-implemented system and method for creating, managing, and reusing schema type definitions in SOA services, grouped in the form of libraries are disclosed. The method in an example embodiment includes: grouping a plurality of Extensible Mark-up Language (XML) schema (XSD) types, each XSD type defined in an individual XSD file; using a processor to bundle the plurality of individual XSD types into a type library, the type library including a type information file to register the individual XSD types in the type library, the type library further including a type dependencies file to register dependencies between the individual XSD types in the same or different type library; importing types from a different type library, when defining derived types or aggregated types; generating Java artifacts from the XSD types; and associating the Java artifacts with corresponding XSD types in the type information file of the type library.

Abstract: A computer-implemented system and method for the definition, creation, management, transmission, and monitoring of errors in a SOA environment.

Abstract: Methods and systems to automatically respond to consider the weight of a request when responding to requests associated with resources are described. In one embodiment, an interface module may be configured to receive a request associated with consumer identifier and a resource. A calculator module may be configured to determine a weight of the request and a usage module configured to calculate, using a processor, a usage level associated with the consumer identifier, the usage level based on a usage history associated with the consumer identifier. An enforcer module may also be configured to respond to the request based on the usage level and the weight of the request. In one embodiment, the usage module may also be configured to update the usage level associated with the consumer identifier based on the weight of the request.

Abstract: A computer-implemented system and method for creating, managing, and reusing schema type definitions in SOA services, grouped in the form of libraries are disclosed. The method in an example embodiment includes: grouping a plurality of Extensible Mark-up Language (XML) schema (XSD) types, each XSD type defined in an individual XSD file; using a processor to bundle the plurality of individual XSD types into a type library, the type library including a type information file to register the individual XSD types in the type library, the type library further including a type dependencies file to register dependencies between the individual XSD types in the same or different type library; importing types from a different type library, when defining derived types or aggregated types; generating Java artifacts from the XSD types; and associating the Java artifacts with corresponding XSD types in the type information file of the type library.

Abstract: A computer-implemented system and method for the definition, creation, management, transmission, and monitoring of errors in a SOA environment.

Abstract: Methods and systems to automatically respond to consider the weight of a request when responding to requests associated with resources are described. In one embodiment, an interface module may be configured to receive a request associated with consumer identifier and a resource. A calculator module may be configured to determine a weight of the request and a usage module configured to calculate, using a processor, a usage level associated with the consumer identifier, the usage level based on a usage history associated with the consumer identifier. An enforcer module may also be configured to respond to the request based on the usage level and the weight of the request. In one embodiment, the usage module may also be configured to update the usage level associated with the consumer identifier based on the weight of the request.

Abstract: A computer-implemented system and method for creating, managing, and reusing schema type definitions in SOA services, grouped in the form of libraries are disclosed. The method in an example embodiment includes: grouping a plurality of Extensible Mark-up Language (XML) schema (XSD) types, each XSD type defined in an individual XSD file; using a processor to bundle the plurality of individual XSD types into a type library, the type library including a type information file to register the individual XSD types in the type library, the type library further including a type dependencies file to register dependencies between the individual XSD types in the same or different type library; importing types from a different type library, when defining derived types or aggregated types; generating Java artifacts from the XSD types; and associating the Java artifacts with corresponding XSD types in the type information file of the type library.

Abstract: A computer-implemented system and method for processing messages using a common interface platform supporting multiple pluggable data formats in a service-oriented pipeline architecture is disclosed. The method in an example embodiment includes deserializing or serializing a request/response message using a pluggable serializer/deserializer mechanism and a corresponding pluggable data format parser. An example embodiment uses a common model for serialization/deserialization regardless of the data format, resulting in a consistent and efficient mechanism.

Abstract: A computer-implemented system and method for creating, managing, and reusing schema type definitions in SOA services, grouped in the form of libraries are disclosed. The method in an example embodiment includes: grouping a plurality of Extensible Mark-up Language (XML) schema (XSD) types, each XSD type defined in an individual XSD file; using a processor to bundle the plurality of individual XSD types into a type library, the type library including a type information file to register the individual XSD types in the type library, the type library further including a type dependencies file to register dependencies between the individual XSD types in the same or different type library; importing types from a different type library, when defining derived types or aggregated types; generating Java artifacts from the XSD types; and associating the Java artifacts with corresponding XSD types in the type information file of the type library.

Abstract: A computer-implemented system and method for processing messages using a common interface platform supporting multiple pluggable data formats in a service-oriented pipeline architecture is disclosed. The method in an example embodiment includes deserializing or serializing a request/response message using a pluggable serializer/deserializer mechanism and a corresponding pluggable data format parser. An example embodiment uses a common model for serialization/deserialization regardless of the data format, resulting in a consistent and efficient mechanism.