Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi-site/pull/17#discussion_r110800166
--- Diff: src/pages/markdown/minifi/getting-started.md ---
@@ -0,0 +1,122 @@
+---
+title: Apache NiFi MiNiFi: Getting Started
+---
+
+# Getting started with MiNiFi
+
+This page explains how to configure and deploy MiNiFi agents.
+
+The Java agent is able to run most of [NiFi's available
processors](http://nifi.apache.org/docs.html), but is a larger binary
distribution (49MB) and consumes greater system resources (24MB max JVM
heapsize by default). If you need maximum flexibility to make routing and
processing decisions at your data's point of origin, the Java agent is a good
fit.
+
+The C++ agent is a smaller binary (3.2MB), consumes low system memory
(about 5MB at idle) but has [a limited subset of
processors](https://github.com/apache/nifi-minifi-cpp#caveats). If your primary
concern is gathering and pushing data to downstream consumers and minimizing
system impact, the C++ agent is a good fit.
+
+
+1. Install the appropriate OS level dependencies:
+
+ #### MiNiFi Java:
+
+ - Java 1.8+
+
+ #### MiNiFi C++:
--- End diff --
I did indeed conflate those, apologies. We do have some considerations in
the current build in terms of dynamically linked items though, such as the
libboost items. I do not believe the current build makes these static.
libxml2 should also no longer be needed. I noticed this was a remnant in
our Travis build and created MINIFI-264 to clean that up.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
