Kelsey, Take it as an opinion from someone new to NiFi (using it for 1 year or so).
I've looked into doing the same thing. The best examples I found were https://pierrevillard.com/2016/04/10/url-shortener-service-with-apache-nifi/comment-page-1/ https://cwiki.apache.org/confluence/display/NIFI/Example+Dataflow+Templates but in the end we decided not to go this route. First, I did not feel good about using embedded Jetty server which I am guessing leaves in the same JVM as NiFi. Second, if you run NiFi cluster, things will be more tricky to manage - how do you load balance requests? how do you provide redundancy if one NiFi node goes down? Probably there are good ways to address these concerns but we decided to use Kafka instead - luckily in our case, the consumer application is flexible to either use web services over rest or can listen to Kafka topics. My conclusion was that it was doable but probably it felt it would be a pain to support production-grade use cases. On Wed, Jun 27, 2018 at 8:38 AM Kelsey RIDER <[email protected]> wrote: > Hello, > > > > I have a project where I’d like NiFi to expose about 4 different RESTful > endpoints. > > The flow behind each of these involves a half-dozen steps and is different > in each case. > > > > I wanted to set it up so that each flow started with a HandleHTTPRequest > processor bound to the appropriate URL path. However, it turns out that two > such processors cannot cohabitate because each one tries to start its own > server bound to the given port. > > I’m wondering: > > - Is there a better way of doing this, without having to have a single > HandleHTTPRequest and making my flows more complicated with all the > required connections to link it to my current entry points? > - Would it be technically possible to have some sort of “HTTPService” > controller that just starts the server and binds to the port, and then > multiple “HTTPServiceListener” processors that use it? Or is it not > possible for a Controller Service to “wake up” a Processor/initiate a flow? > > > > Thanks for the help, > > > > Kelsey > Suite à l’évolution des dispositifs de réglementation du travail, si vous > recevez ce mail avant 7h00, en soirée, durant le week-end ou vos congés > merci, sauf cas d’urgence exceptionnelle, de ne pas le traiter ni d’y > répondre immédiatement. >
