[
https://issues.apache.org/jira/browse/NIFI-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Sargrad updated NIFI-6590:
--------------------------------
Description:
I've been using NiFi for about a year now. I've built a number of data
ingest/egress flows with it. We've also built about 5 custom processors (in
JAVA). I've not really used it as a command & control framework.
I am considering using NiFi for a couple of mechanisms and I'd like the experts
view as to whether or not this is an appropriate use of the NiFi application
framework.
Would you use NiFi for the following types of functions:
* RESTful service - Expose and API, and respond to CRUD RESTful operations
* Data Replay Service - Reach into a database (e.g. Kafka, HDFS, Mongo, etc),
and replay data in a temporal fashion
A data replay service, might, for example, be built as a custom NiFi processor
that creates a thread, and creates one or more flowfiles periodically based on
the configuration of that processor. The key is this service implements a
timeline such that flowfiles are generated through time, based on the timing
characteristics of the data in the database. It might run for days at a time.
Currently we might build such a service as a background daemon, perhaps
implemented using Node JS (or of course, more traditional languages like java,
c/c++).
A RESTful service might, for example, be built as a custom NiFi processor that
exposes an API (e.g. an OPEN API compliant API), and responds to commands
against that API. Currently we build and expose such service APIs using Node
Express.
Thoughts from the experts are appreciated.
was:
I've been using NiFi for about a year now. I've built a number of data
ingest/egress flows with it. We've also built about 5 custom processors (in
JAVA). I've not really used it as a command & control framework.
I am considering using NiFi for a couple of mechanisms and I'd like the experts
view as to whether or not this is an appropriate use of the NiFi application
framework.
Would you use NiFi for the following types of functions:
* RESTful service - Expose and API, and respond to CRUD RESTful operations
* Data Replay Service - Reach into a database (e.g. Kafka, HDFS, Mongo, etc),
and replay data in a temporal fashion
A data replay service, might, for example, be built as a custom NiFi processor
that creates a thread, and creates one or more flowfiles periodically based on
the configuration of that processor. Currently we might build such a service as
a background daemon, perhaps implemented using Node JS (or of course, more
traditional languages like java, c/c++).
A RESTful service might, for example, be built as a custom NiFi processor that
exposes an API (e.g. an OPEN API compliant API), and responds to commands
against that API. Currently we build and expose such service APIs using Node
Express.
Thoughts from the experts are appreciated.
> NiFi Command & Control Framework
> --------------------------------
>
> Key: NIFI-6590
> URL: https://issues.apache.org/jira/browse/NIFI-6590
> Project: Apache NiFi
> Issue Type: Wish
> Environment: Centos 7
> Reporter: David Sargrad
> Priority: Trivial
>
> I've been using NiFi for about a year now. I've built a number of data
> ingest/egress flows with it. We've also built about 5 custom processors (in
> JAVA). I've not really used it as a command & control framework.
>
> I am considering using NiFi for a couple of mechanisms and I'd like the
> experts view as to whether or not this is an appropriate use of the NiFi
> application framework.
>
> Would you use NiFi for the following types of functions:
>
> * RESTful service - Expose and API, and respond to CRUD RESTful operations
> * Data Replay Service - Reach into a database (e.g. Kafka, HDFS, Mongo,
> etc), and replay data in a temporal fashion
>
> A data replay service, might, for example, be built as a custom NiFi
> processor that creates a thread, and creates one or more flowfiles
> periodically based on the configuration of that processor. The key is this
> service implements a timeline such that flowfiles are generated through time,
> based on the timing characteristics of the data in the database. It might run
> for days at a time. Currently we might build such a service as a background
> daemon, perhaps implemented using Node JS (or of course, more traditional
> languages like java, c/c++).
>
> A RESTful service might, for example, be built as a custom NiFi processor
> that exposes an API (e.g. an OPEN API compliant API), and responds to
> commands against that API. Currently we build and expose such service APIs
> using Node Express.
>
> Thoughts from the experts are appreciated.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
