Details

    • Type: Rice Research Item
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Component/s: KSB
    • Labels:
      None
    • Rice Theme:
      Service Orientation
    • Priority Score:
      5
    • Functional Justification :
      This item includes no real functional impact.
    • Technical Justification:
      Hide
      As per the "not invented here" principal espoused in the Kuali Rice charter, utilizing other open source projects that provide the functionality we need as opposed to rolling our own should be our preferred solution. The Kuali Service Bus works but is very light on features which could potential limit it's capabilities in real enterprise production environments. Other open source service bus implementations like ServiceMix or Mule are much more widely deployed than the KSB and also benefit from being projects that are focussed on the ESB problem. If we were able to replace some or all of KSB with already built open source solutions, that would reduce the footprint and maintenance costs of the Rice project.
      Show
      As per the "not invented here" principal espoused in the Kuali Rice charter, utilizing other open source projects that provide the functionality we need as opposed to rolling our own should be our preferred solution. The Kuali Service Bus works but is very light on features which could potential limit it's capabilities in real enterprise production environments. Other open source service bus implementations like ServiceMix or Mule are much more widely deployed than the KSB and also benefit from being projects that are focussed on the ESB problem. If we were able to replace some or all of KSB with already built open source solutions, that would reduce the footprint and maintenance costs of the Rice project.
    • Impact if not Implemented:
      We would have to continue to maintain the KSB codebase and likely work on some significant enhancements to it to keep it relevant and provides the features that implementers expect from an enterprise service bus solution.
    • Priority - KFS:
      Low
    • Priority - KC:
      Low
    • Priority - KS:
      Low
    • Priority - Rice:
      Medium
    • Theme:
      Adopting Existing Code
    • Application Impact:
      High
    • Effort Estimate:
      High ~ 1000 hrs

      Description

      The Kuali Rice project currently implements a custom service bus (which is really more of a service registry then a pure service bus). There are other open-source service bus implementations out there which have evolved in parallel to the KSB and offer additional functionality. It is advisable that we investigate these other options and determine the value in making this switch.

      Summary of Work Involved: The Kuali Rice project currently implements a custom service bus (which is really more of a service registry then a pure service bus). There are other open-source service bus implementations out there which have evolved in parallel to the KSB and offer additional functionality. It is advisable that we investigate these other options and determine the value in making this switch. As per the "not invented here" principal espoused in the Kuali Rice charter, utilizing other open source projects that provide the functionality we need as opposed to rolling our own should be our preferred solution. The Kuali Service Bus works but is very light on features which could potential limit it's capabilities in real enterprise production environments. Other open source service bus implementations like ServiceMix or Mule are much more widely deployed than the KSB and also benefit from being projects that are focussed on the ESB problem. If we were able to replace some or all of KSB with already built open source solutions, that would reduce the footprint and maintenance costs of the Rice project. It should be noted that while this would be a backend change and would make Rice and it's applications better, the general enduser would likely see no immediate change. This would be a fairly large research item due to the reliance on the KSB that Rice currently has and testing out the option(s) before picking a replacement would require additional time.

        Attachments

          Issue Links

            Activity

            Hide
            cfairlie Cath Fairlie (Inactive) added a comment -

            KS originally selected Service Mix as our preferred ESB, but later had to drop it. Service Mix moved to re-architect their product and as yet have not shown any progress. We would rather see Rice move towards integration of KSB with other ESB products. Any product to replace KSB must meet all of our needs first.

            Show
            cfairlie Cath Fairlie (Inactive) added a comment - KS originally selected Service Mix as our preferred ESB, but later had to drop it. Service Mix moved to re-architect their product and as yet have not shown any progress. We would rather see Rice move towards integration of KSB with other ESB products. Any product to replace KSB must meet all of our needs first.
            Hide
            ewestfal Eric Westfall added a comment - - edited

            This has come up multiple times when Rice is being evaluated for use at another institution so it seems like the research into this is important which is why we are setting as Medium from a Rice/non-kuali client application perspective so we can communicate what our short/medium/long terms plans are surrounding KSB.

            Show
            ewestfal Eric Westfall added a comment - - edited This has come up multiple times when Rice is being evaluated for use at another institution so it seems like the research into this is important which is why we are setting as Medium from a Rice/non-kuali client application perspective so we can communicate what our short/medium/long terms plans are surrounding KSB.
            Hide
            coppola Chris Coppola (Inactive) added a comment -

            Eric, your effort estimate seems to be for actually replacing the KSB. This item is simply doing the research. If I'm correct, can you please update the effort estimate?

            My guess is that we also need to better define the research output as well.

            Show
            coppola Chris Coppola (Inactive) added a comment - Eric, your effort estimate seems to be for actually replacing the KSB. This item is simply doing the research. If I'm correct, can you please update the effort estimate? My guess is that we also need to better define the research output as well.
            Hide
            coppola Chris Coppola (Inactive) added a comment -

            Eric, I'm assigning this to you based on my previous comment about the effort estimate.

            Show
            coppola Chris Coppola (Inactive) added a comment - Eric, I'm assigning this to you based on my previous comment about the effort estimate.
            Hide
            lschultz Lori Schultz (Inactive) added a comment -

            I would like to understand how the impact of a replacement, and how it impacts potential decisions to implement.

            Show
            lschultz Lori Schultz (Inactive) added a comment - I would like to understand how the impact of a replacement, and how it impacts potential decisions to implement.
            Hide
            ewestfal Eric Westfall added a comment -

            Regarding Lori's question, one major concern I have which would need to be addressed is the maintenance and deployment overhead of something like ServiceMix vs. the Kuali Service Bus. KSB is mostly hidden from implementors of Kuali software. I think this is largely related to the fact that it does just enough to provide the kuali applications with the functionality they need for messaging, service discovery, and remoting. To that end, these other products provide many more capabilities, but the general architecture and deployment options are different from KSB. This could potentially make configuration and administration of kuali-rice based applications more difficult.

            Note however that this is largely conjecture on my part based on past experience with components of these ESBs such as ActiveMQ. It is possible that the modern -day experience with these software packages is more "user" friendly. I have not devoted any notable amount of time yet to researching this particular topic and probably won't unit this bubble's up in the roadmap.

            Show
            ewestfal Eric Westfall added a comment - Regarding Lori's question, one major concern I have which would need to be addressed is the maintenance and deployment overhead of something like ServiceMix vs. the Kuali Service Bus. KSB is mostly hidden from implementors of Kuali software. I think this is largely related to the fact that it does just enough to provide the kuali applications with the functionality they need for messaging, service discovery, and remoting. To that end, these other products provide many more capabilities, but the general architecture and deployment options are different from KSB. This could potentially make configuration and administration of kuali-rice based applications more difficult. Note however that this is largely conjecture on my part based on past experience with components of these ESBs such as ActiveMQ. It is possible that the modern -day experience with these software packages is more "user" friendly. I have not devoted any notable amount of time yet to researching this particular topic and probably won't unit this bubble's up in the roadmap.

              People

              • Assignee:
                ewestfal Eric Westfall
                Reporter:
                coppola Chris Coppola (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: