<story><title>Maestro: Netflix&apos;s Workflow Orchestrator</title><url>https://netflixtechblog.com/maestro-netflixs-workflow-orchestrator-ee13a06f9c78</url></story><parent_chain><item><author>slt2021</author><text>So Netflix expects open source community to pick up the maintenance tab ?&lt;p&gt;I understand how open source proejcts are born, but I struggle to see what is novelty of this project. Just another Java CRUD app with some questionable design choices that are only applicable to netflix:&lt;p&gt;1. They claim it is distributed system, but it is just a regular Java crud with SQL backend&lt;p&gt;2. Java-like DSL with parser and classloader (why? Just why?)&lt;p&gt;Projects like these are the perfect examples of Enterprise Grade FizzBuzz (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;EnterpriseQualityCoding&amp;#x2F;FizzBuzzEnterpriseEdition&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;EnterpriseQualityCoding&amp;#x2F;FizzBuzzEnterpris...&lt;/a&gt;) and this is exactly what I dont like about it</text></item><item><author>cortesoft</author><text>Isn&amp;#x27;t this exactly WHY this blog post exists? They are open sourcing this software so that they don&amp;#x27;t have to maintain it all internally anymore.&lt;p&gt;They had a need that an existing &amp;quot;off-the-shelf open source&amp;quot; project didn&amp;#x27;t solve, so they created this an are now turning it into an &amp;quot;off-the-shelf open source&amp;quot; project so they can keep using it without having to maintain it entirely themselves.&lt;p&gt;How are these open source tools supposed to be created in the first place? This is the process, someone has to do it</text></item><item><author>slt2021</author><text>I used to be impressed with these corporate techblogs and their internal proprietary systems, but not so much anymore. Because code is a liability.&lt;p&gt;I would rather use off-the-shelf open source stuff with long history of maintenance and improvement, rather than reinvent the cron&amp;#x2F;celery&amp;#x2F;airflow&amp;#x2F;whatever, because code is a liability. Somebody needs to maintain it, fix bugs, add new features. Unless I get +1 grade promotion and salary&amp;#x2F;rsu bump, ofc.&lt;p&gt;People need to realize that code is a liability, anything that is not the business critical stuff that earns&amp;#x2F;makes $$$ for the company is a distraction and resource sink.</text></item></parent_chain><comment><author>cortesoft</author><text>&amp;gt; So Netflix expects open source community to pick up the maintenance tab?&lt;p&gt;Isn’t this the deal with all open source? They are giving something (the code and access to the project) in return for help maintaining it?&lt;p&gt;No one is being forced to do anything. It is not like there is some open source contributor somewhere now saying, “oh damn, now I have to maintain this, too?”&lt;p&gt;If people like it and find value in it, they can help contribute to the project in ways they want. Netflix gets to use those contributions, in return for letting people use their contributions. That is just how open source works.</text></comment>
<story><title>Maestro: Netflix&apos;s Workflow Orchestrator</title><url>https://netflixtechblog.com/maestro-netflixs-workflow-orchestrator-ee13a06f9c78</url></story><parent_chain><item><author>slt2021</author><text>So Netflix expects open source community to pick up the maintenance tab ?&lt;p&gt;I understand how open source proejcts are born, but I struggle to see what is novelty of this project. Just another Java CRUD app with some questionable design choices that are only applicable to netflix:&lt;p&gt;1. They claim it is distributed system, but it is just a regular Java crud with SQL backend&lt;p&gt;2. Java-like DSL with parser and classloader (why? Just why?)&lt;p&gt;Projects like these are the perfect examples of Enterprise Grade FizzBuzz (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;EnterpriseQualityCoding&amp;#x2F;FizzBuzzEnterpriseEdition&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;EnterpriseQualityCoding&amp;#x2F;FizzBuzzEnterpris...&lt;/a&gt;) and this is exactly what I dont like about it</text></item><item><author>cortesoft</author><text>Isn&amp;#x27;t this exactly WHY this blog post exists? They are open sourcing this software so that they don&amp;#x27;t have to maintain it all internally anymore.&lt;p&gt;They had a need that an existing &amp;quot;off-the-shelf open source&amp;quot; project didn&amp;#x27;t solve, so they created this an are now turning it into an &amp;quot;off-the-shelf open source&amp;quot; project so they can keep using it without having to maintain it entirely themselves.&lt;p&gt;How are these open source tools supposed to be created in the first place? This is the process, someone has to do it</text></item><item><author>slt2021</author><text>I used to be impressed with these corporate techblogs and their internal proprietary systems, but not so much anymore. Because code is a liability.&lt;p&gt;I would rather use off-the-shelf open source stuff with long history of maintenance and improvement, rather than reinvent the cron&amp;#x2F;celery&amp;#x2F;airflow&amp;#x2F;whatever, because code is a liability. Somebody needs to maintain it, fix bugs, add new features. Unless I get +1 grade promotion and salary&amp;#x2F;rsu bump, ofc.&lt;p&gt;People need to realize that code is a liability, anything that is not the business critical stuff that earns&amp;#x2F;makes $$$ for the company is a distraction and resource sink.</text></item></parent_chain><comment><author>geodel</author><text>You are making great points. This is power of Netflix marketing and branding that they are considered as cutting edge tech company. In reality most of Netflix Java projects are pretty mediocre Enterprise Java stuff. Last year or so they have mandated Spring Boot as their development platform for all their web services.&lt;p&gt;This is exactly same stack I have to deal daily and management reason is it is lowest common denominator that works well with 3-month contract developer to deliver Nth micro service whose sole job is to call another service.</text></comment>