19. A message handler comprising: a network interface to: accept a service request, the service request including client information and client data received from a sender, the client information including a plurality of tasks, and forward a backend message; a validator to: validate the service request to determine whether the sender is authorized, and determine whether the client information and the client data are valid; a translator to: translate the service request using a first schema that is defined by a client, the first schema including: a base information section for storing at least one of: information associated with the sender, information associated with a receiver of the service request, or information identifying the first schema, an account information section for storing: identifier information associated with the client, or identifier information associated with a contact associated with the client, an asset information section for storing: data about hardware associated with the service request, or data about software associated with the service request, and an activity information section for storing information identifying activities associated with the service request; and parse the service request, using the first schema, to extract the client information and the client data; and a publisher to: provide the backend message to the network interface in a format defined by a backend schema, the backend message including valid client information and valid client data, send the backend message to a database accessible to a backend system associated with operating on the valid client data, the backend system including a plurality of backend devices, and send a notification only to particular backend devices, of the plurality of backend devices, informing the particular backend devices that the backend message has been sent to the database, the plurality of tasks being relevant to the particular backend devices.
19. A message handler comprising: a network interface to: accept a service request, the service request including client information and client data received from a sender, the client information including a plurality of tasks, and forward a backend message; a validator to: validate the service request to determine whether the sender is authorized, and determine whether the client information and the client data are valid; a translator to: translate the service request using a first schema that is defined by a client, the first schema including: a base information section for storing at least one of: information associated with the sender, information associated with a receiver of the service request, or information identifying the first schema, an account information section for storing: identifier information associated with the client, or identifier information associated with a contact associated with the client, an asset information section for storing: data about hardware associated with the service request, or data about software associated with the service request, and an activity information section for storing information identifying activities associated with the service request; and parse the service request, using the first schema, to extract the client information and the client data; and a publisher to: provide the backend message to the network interface in a format defined by a backend schema, the backend message including valid client information and valid client data, send the backend message to a database accessible to a backend system associated with operating on the valid client data, the backend system including a plurality of backend devices, and send a notification only to particular backend devices, of the plurality of backend devices, informing the particular backend devices that the backend message has been sent to the database, the plurality of tasks being relevant to the particular backend devices. 20. The message handler of claim 19 , where the first schema is operatively associated with a schema database.