[jira] [Commented] (NIFI-5922) Stateless NiFi, an alternative runtime for NiFi flows

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-5922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844980#comment-16844980 ] 

ASF subversion and git services commented on NIFI-5922:
-------------------------------------------------------

Commit cbafd8f834813f4e23c961a282a6f44b5a62c078 in nifi's branch refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=cbafd8f ]

NIFI-5922: Addressed checkstyle violations; added to README Updates to nifi-fn proposal:
- Separated into nifi-fn-core, nifi-fn-bootstrap, nifi-fn-nar, nifi-fn-assembly; fully unpacks nars and runs flows
- Rebased against master and updated to version 1.10.0-SNAPSHOT
- Removed dependency on nifi-framework-core
- Added LICENSE/NOTICE files


> Stateless NiFi, an alternative runtime for NiFi flows
> -----------------------------------------------------
>
>                 Key: NIFI-5922
>                 URL: https://issues.apache.org/jira/browse/NIFI-5922
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Sam Hjelmfelt
>            Priority: Major
>          Time Spent: 3h 50m
>  Remaining Estimate: 0h
>
> NiFi-Fn is a library for running NiFi flows as stateless functions. It provides similar delivery guarantees as NiFi without the need for on-disk repositories by waiting to confirm receipt ofincoming data until it has been written to the destination. This is similar to Storm’s acking mechanism and Spark’s interface for committing Kafka offsets, except that in NiFi-Fn, this is completely handled by the framework while still supporting all NiFi processors and controller services natively without change.This results in the ability to run NiFi flows as ephemeral, stateless functions and should be able to rival MirrorMaker, Distcp, and Scoop for performance,efficiency, and scalability while leveraging the vast library of NiFi processors and the NiFi UI for building custom flows.
> By leveraging container engines (e.g.YARN, Kubernetes), long-running NiFi-Fn flows can be deployed that take full advantage of the platform’s scale and multi-tenancy features. By leveraging Function as a Service engines (FaaS) (e.g. AWS Lambda, Apache OpenWhisk), NiFi-Fn flows can be attached to event sources (or just cron) for event-driven data movement where flows only run when triggered and pricing is measured at the 100ms granularity. By combining the two, large-scale batch processing could also be performed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)