kaxil commented on a change in pull request #385:
URL: https://github.com/apache/airflow-site/pull/385#discussion_r579718181
##########
File path: landing-pages/site/content/en/blog/airflow-survey-2020/index.md
##########
@@ -0,0 +1,426 @@
+---
+title: "Airflow Survey 2020"
+linkTitle: "Airflow Survey 2020"
+author: "Tomek Urbaszek"
+twitter: "turbaszek"
+github: "turbaszek"
+linkedin: "tomaszurbaszek"
+description: "AAAAAAAA"
+tags: ["community", "survey", "users"]
+date: "2020-02-15"
+---
+# Apache Airflow Survey 2020
+
+World of data processing tools is growing steadily.
+
+It's important to note that the 2020 survey was still mostly about 1.10.X
version of Apache Airflow and
+possibly many of drawbacks was addressed in 2.0 version that was released in
December 2020. But if this
+is true, we will learn next year!
+
+
+## Overview of the user
+
+**What best describes your current occupation?**
+
+| | No. | % |
+|---------------------|-------|-------|
+| Data Engineer | 115 | 56.65 |
+| Developer | 28 | 13.79 |
+| DevOps | 17 | 8.37 |
+| Solutions Architect | 14 | 6.9 |
+| Data Scientist | 12 | 5.91 |
+| Other | 10 | 4.93 |
+| Data Analyst | 4 | 1.97 |
+| Support Engineer | 3 | 1.48 |
+
+Those results are not a surprise as Airflow is a tool dedicated to
data-related tasks. The majority of
+our users are data engineers, scientists or analysts. The 2020 results are
similar to those from 2019 with
+visible slight increase in ML use cases.
+
+Additionally, 79% of users uses Airflow on daily basis and 16% interacts with
it at least once a week.
+
+**How many people work in your company?**
+
+| | No. | % |
+|--------|-------|-------|
+| 200+ | 107 | 52.71 |
+| 51-200 | 44 | 21.67 |
+| 11-50 | 37 | 18.23 |
+| 1-10 | 15 | 7.39 |
+
+**How many people in your company use Airflow?**
+
+| | No. | % |
+|-------|-------|-------|
+| 1-5 | 84 | 41.38 |
+| 6-20 | 75 | 36.95 |
+| 21-50 | 23 | 11.33 |
+| 50+ | 21 | 10.34 |
+
+Airflow is a software that is used and trusted by big companies. We can also
see that Airflow can work
+fine for teams of different sizes. However, in some cases users may use
multiple Airflow instances.
+
+
+**Are you considering moving to other workflow engines?**
+
+| | No. | % |
+|-------------------------------|-------|-------|
+| No, we are happy with Airflow | 174 | 85.71 |
+| Yes | 29 | 14.29 |
+
+Nearly 1 out of 7 users is considering migrating to other workflow engine.
Their decision is usually
+justified by need of **easier workflow writing experience** (12.32%), **better
UI/UX** and **faster scheduler**
+(8.37% both).
+
+While the first point may be addressed by (TaskFlow API)[link] in Airflow 2.0
the other two are definitely addressed
+in the new major version. And the early feedback from 2.0 users seems to be
confirming it.
+
+The alternative engines considered by users are mainly Prefect and Argo. Some
participants mentioned also
+Luigi, Kubeflow or custom solutions.
+
+
+**Are you or your team actively participating in Airflow development -
contributing?**
+
+| | No. | % |
+|-----------------|-------|-------|
+| I wish we could | 99 | 48.77 |
+| No | 59 | 29.06 |
+| Yes | 45 | 22.17 |
+
+This is really heart-warming result. It means that 1 out of 5 users
contributes actively to our project!
+But it would be good to learn if there's something else than time that is
stopping people who wish to contribute
+from doing it. If there are some other obstacles we definitely would like to
learn about them so we can improve.
+That said - if you know something we can improve please reach out to use
either via slack, dev list or Github
+discussions.
+
+**How likely are you to recommend Apache Airflow?**
+
+| | No. | 2020 % | 2019 % |
+|---------------|-------|--------|--------|
+| Very Likely | 125 | 61.58 | 45.45% |
+| Likely | 62 | 30.54 | 40.26% |
+| Neutral | 11 | 5.42 | 10.71% |
+| Unlikely | 3 | 1.48 | 2.60% |
+| Very unlikely | 2 | 0.99 | 0.97% |
+
+Here is a good news! It seems that people are more willing to recommend Apache
Airflow than year before.
+
+**What is your source of information about Airflow?**
+
+| | No. | % |
+|-----------------------------------|-------|-------|
+| Documentation | 154 | 75.86 |
+| Airflow website | 139 | 68.47 |
+| Slack | 128 | 63.05 |
+| Github | 127 | 62.56 |
+| Stack Overflow | 72 | 35.47 |
+| Airflow Summit Videos | 44 | 21.67 |
+| The dev mailing list | 33 | 16.26 |
+| Awesome Apache Airflow repository | 21 | 10.34 |
+| Other | 15 | 7.39 |
+
+Here we see that Airflow documentation is the crucial source of information.
What's interesting is that more
+than 60% of users are getting information from Github and Slack channels.
+
+
+
+## Airflow uses cases
+
+**Do you have any customisation of Airflow?**
+
+| | No. | % |
+|--------------------------------------|-------|-------|
+| No, we use vanilla Airflow | 154 | 75.86 |
+| Yes, we have small patches (no fork) | 34 | 16.75 |
+| Yes, we have separate fork | 15 | 7.39 |
+
+**When onboarding new members to airflow, what is the biggest problem?**
+
+| | No. |
% |
+|-----------------------------------------------------------------|-------|-------|
+| No guide on best practises on developing DAGs | 102 |
50.25 |
+| There is no easy option to launch Airflow | 64 |
31.53 |
+| Small number of tutorials on different aspects of using Airflow | 57 |
28.08 |
+| Documentation is not clear enough | 53 |
26.11 |
+| There is no easy option to deploy DAGs to an Airflow instance | 52 |
25.62 |
+| No problems | 34 |
16.75 |
+| Small number of blogs regarding Airflow | 30 |
14.78 |
+
+**Which interface(s) of Airflow do you use as part of your current role?**
+
+| | No. | % |
+|-------------------------------------------------------|-------|-------|
+| Original Airflow Graphical User Interface | 199 | 98.03 |
+| CLI | 88 | 43.35 |
+| API | 48 | 23.65 |
+| Custom (own created) Airflow Graphical User Interface | 12 | 5.91 |
+| Other | 3 | 1.48 |
+
+**Do you combine multiple DAGs?**
+
+| | No. | % |
+|------------------------------------|-------|-------|
+| Yes, by triggering another DAG | 87 | 42.86 |
+| No, I don't combine multiple DAGs | 79 | 38.92 |
+| Yes, through SubDAG | 40 | 19.7 |
+| Other | 18 | 8.87 |
+
+
+**How do you integrate with external services?**
+
+| | No. | % |
+|---------------------------------------------|-------|-------|
+| Using existing dedicated operators / hooks | 147 | 72.41 |
+| Using Bash / Python operator | 140 | 68.97 |
+| Using own custom operators / hooks | 138 | 67.98 |
+| Other | 12 | 5.91 |
+
+**What external services do you use in your Airflow DAGs?**
+
+| | No. | % |
+|---------------------------------------------------|-------|-------|
+| Amazon Web Services | 121 | 59.61 |
+| Internal company systems | 113 | 55.67 |
+| Google Cloud Platform / Google APIs | 97 | 47.78 |
+| Hadoop / Spark / Flink / Other Apache software | 72 | 35.47 |
+| Microsoft Azure | 21 | 10.34 |
+| Other | 19 | 9.36 |
+| I do not use external services in my Airflow DAGs | 5 | 2.46 |
+
+
+
+**Do you use Airflow Plugins? If yes, what do you use them for?**
+
+| | No. | % |
+|----------------------------------------|-------|-------|
+| Adding new operators/sensors and hooks | 119 | 58.62 |
+| I don't use Airflow plugins | 69 | 33.99 |
+| Adding AppBuilder views & menu items | 27 | 13.3 |
+| Adding new executors | 17 | 8.37 |
+| Adding OperatorExtraLinks | 13 | 6.4 |
+| Other
+
+**Do you use Airflow's data lineage feature?**
+
+| | No. | % |
+|------------------------------------------------------------|-------|-------|
+| No, I will use such feature if fully supported in Airflow | 105 | 51.72 |
+| No, data lineage isn’t a concern for my usage. | 68 | 33.5 |
+| Yes, I use another data lineage product | 24 | 11.82 |
+| Yes, I use custom implementation | 5 | 2.46 |
+| Yes, I use Airflow's experimental data lineage feature | 1 | 0.49 |
+
+When asked what lineage product user use the answers were varying from custom
tools
+to known product like Amundsen, Atlas or dbt.
+
+## Deployment
+
+**How many active DAGs do you have in your largest Airflow instance? **
+
+| Number of DAGs | No. | % |
+|-------------------|-------|-----|
+| < 20 | 64 | 32 |
+| 21-40 | 33 | 16 |
+| 41-60 | 13 | 6 |
+| 61-100 | 32 | 16 |
+| 101-200 | 31 | 15 |
+| 201-300 | 8 | 4 |
+| 301-999 | 12 | 6 |
+| 1000+ | 10 | 5
Review comment:
```suggestion
| 1000+ | 10 | 5 |
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
