Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-4496

Speed Test: Soap vs java serialization for our remoted services

    Details

    • Type: Task
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.0.3
    • Fix Version/s: 2.0
    • Labels:
      None
    • Rice Module:
      KIM
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required

      Description

      Rice currently defaults to java serialization for remoting... instead of SOAP. This is primarily due to performance reason.

      One issue with using serialization is that switching JVM's could cause differences in the way objects are serialized. ex. Java 5 client connecting to java 6 server.

      We need to run some speed tests to see which is faster, soap or searial for remoted services.

      For this particular case we upgrading the recipe sample app to spring 1.0.3 (snapshot) and tested that against the standalone server.
      We created a simple servlet inside the sample app. All this servlet does is take in a request param to switch the underlying service call to use serialization or soap remoting.

      Our test calls the identityService.lookupEntityInfo with an empty map. This will return a relatively large payload.

      We're testing:
      Soap vs Java Serialization

      Oracle vs MySql

      Soap Security On/off

        Attachments

          Activity

          Error rendering 'com.atlassian.jira.jira-view-issue-plugin:activitymodule'. Please contact your JIRA administrators.

            People

            • Assignee:
              ewestfal Eric Westfall
              Reporter:
              gtaylor Garey Taylor
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: