[UIMA-5280] UIMA-AS V3: Redesign to simplify embedding in applications

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 3.0.1AS
• Component/s: Async Scaleout
• Assignee: Jaroslaw Cwiklik
• Reporter: Jaroslaw Cwiklik
• Created: 27/Jan/17 17:34
• Updated: 19/Jul/17 17:20

Description

The current UIMA-AS runtime requires an ActiveMQ broker to be running to support message exchanges between an application and UIMA-AS based service. An application uses the UIMA-AS client API to send CASes to a service for analysis. A CAS is serialized by the client, wrapped in a Message object and delivered to a JMS queue. A service than dequeues the message and deserializes a CAS contained within it. Reverse happens on a reply. In total, such exchange requires two serializations and two deserializations of the CAS.

To avoid such overhead, a collocated service deployment in the new design will use java queues for transport and pass a CAS by reference.

Sub-Tasks

• UIMA-AS V3: Replace dd2spring with java based DD processing: Open
• UIMA-AS V3: Refactor code to support deploying services without a broker: Open
• UIMA-AS V3: add support for compress serialization form 4 and 6: Open