I wonder how practical it is to use NiFi as a server to serve web service
calls and return data over REST to consumers. It seems like a natural fit,
given NiFi's scalability and redundancy and a host of data integration and
transformation processors.
I am thinking to create a quick pilot using Kaf
I think you would hit two big barriers in design:
1. NiFi just isn't designed to be an app server for additional service
layer components a la Tomcat.
2. Synchronizing between the REST services and NiFi's highly asynchronous
processing would be a logistical nightmare if your goal is to confine NiF
thanks Mike, you've reasoned my concerns as well.
On Mon, Mar 26, 2018 at 5:57 PM, Mike Thomsen
wrote:
> I think you would hit two big barriers in design:
>
> 1. NiFi just isn't designed to be an app server for additional service
> layer components a la Tomcat.
> 2. Synchronizing between the RES