<div id="readability-page-1" class="page"><div>
<section data-height="100" data-opacity="0.3">

<header>
<p><a href="https://jaigouk.com/"><img src="https://files.jaigouk.com/2018/08/jaigouk-blog-logo.png" alt="Jaigouk.Kim"></a>
</p>
<nav>
<ul>
<li>
<a href="https://jaigouk.com/">Home</a>
</li>
<li>
<a href="https://jaigouk.com/about/">About</a>
</li>
<li>
<a href="https://jaigouk.com/tag/posts-tag/">Posts</a>
</li>
<li>
<a href="https://jaigouk.com/projects/">Projects</a>
</li>
<li>
<a href="https://jaigouk.com/contact/">Contact</a>
</li>
</ul>
<ul>
<li>
<span>
<svg>
<use xlink:href="/assets/svg/icons.svg?v=546e9e9eb5#menu"></use>
</svg>
</span>
</li>
</ul>
</nav>
</header>
<section>

<h2>
Introducing OpenFaaS to the company
</h2>
<p>
personal experience about spreading openfaas at work
</p>
</section>

</section>
<section>
<p>My motivations to use openfaas were,</p><ul><li>learning tool for new languages</li><li>getting used to kubernetes</li><li>learn serverless architecture with no cost for aws</li></ul><p>I gave a tech talk to other developers at work with a demo and some people asked me to form a workshop. So, I cloned <a href="https://github.com/openfaas/workshop/">openfaas workshop repo</a> and I got a permission from head of engineering to go through it 1 hour per week. In the beginning there were 17 devs. as time passes, people were not able to attend it because they were simply busy with their work. </p><p>Some people followed the lab notes if they were not able to attend the workshop. we have following lab note structure.</p><pre><code>## Lab 5 - Create a Gitbot

[official openfaas lab5 note](https://github.com/openfaas/workshop/blob/master/lab5.md)


** feel free to update our notes.**

TOC

1. following the offical lab note
2. what we learned
3. ref
</code></pre>
<p>After 10th workshop session is done, i wanted to push this to the next phase. But there were concerns about openfaas from other devs. It's still young and people didn't want to use it for our production environment. But it is ok to use it for internal tools. Not used for production but the impact can be huge based on the problem I tackle. Luckily, head of frontend team was enthusiastic about using openfaas. Because i told him that i was able to write graphql functions that are connected to Neo4j. It needs to be polished but i was able to show the working query. &nbsp;The guy had a real problem. It was about having lots of PRs that are hanging for a long time. The repository is a legacy codes. And people hate to dive into legacy codes. Well, as a "smart developer", you can find ways to avoid the situation. in the end, the legacy repository ended up with those PRs that are waiting people to review and QA. It's not about serverless architecture. it's about code ownership and having a solid CI/CD work process. I suggested him to form a plan to do that. git-ops can be a candidate if it's well crafted with QA steps.</p><p>There might something I can help. And then I remembered OpenFaaS community is using <a href="https://github.com/alexellis/derek">Derek</a> - a serverless 🤖 to manage PRs and issues. </p><iframe width="560" height="315" src="https://www.youtube.com/embed/ccoeut-Psuw" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen=""></iframe><p>If we add more "pipe lines" that makes sense to the frontend team, then we can use it to improve our daily work process. Yes, I agree that it's more about people problem. but it will accelerate the plan. Now, I found a chance to use openfaas at work at last. Good thing about my situation is that our backend will be broken into services and we're going to use kafka as our message queue. And it's possible to launch openfaas function with kafka-connector. (<a href="https://docs.openfaas.com/reference/triggers/">you can trigger your functions via sns, rabbit mq and cloud events too</a>) </p><p>People will see it working and feel good about derek and automation for chores. If people start to add more features or functions then they might want to replicate the experience for production environment. we can do it with "stable" service like aws lambda in the beginning but it will cost money. then openfaas is a good option. isn't it?</p>
</section>

<div>
<p><a href="/author/jaigouk/">
<img src="https://www.gravatar.com/avatar/dfa5114caa61dd2b010e998cff905d73?s=250&amp;d=mm&amp;r=x" alt="Jaigouk KIm">
</a></p>
</div>


</div></div>

Jaigouk.Kim

My motivations to use openfaas were,
learning tool for new languages
getting used to kubernetes
learn serverless architecture with no cost for aws
I gave a tech talk to other developers at work with a demo and some people asked me to form a workshop. So, I cloned openfaas workshop repo and I got a permission from head of engineering to go through it 1 hour per week. In the beginning there were 17 devs. as time passes, people were not able to attend it because they were simply busy with their work. 
Some people followed the lab notes if they were not able to attend the workshop. we have following lab note structure.
## Lab 5 - Create a Gitbot
[official openfaas lab5 note](https://github.com/openfaas/workshop/blob/master/lab5.md)
** feel free to update our notes.**
TOC
1. following the offical lab note
2. what we learned
3. ref
After 10th workshop session is done, i wanted to push this to the next phase. But there were concerns about openfaas from other devs. It's still young and people didn't want to use it for our production environment. But it is ok to use it for internal tools. Not used for production but the impact can be huge based on the problem I tackle. Luckily, head of frontend team was enthusiastic about using openfaas. Because i told him that i was able to write graphql functions that are connected to Neo4j. It needs to be polished but i was able to show the working query.  The guy had a real problem. It was about having lots of PRs that are hanging for a long time. The repository is a legacy codes. And people hate to dive into legacy codes. Well, as a "smart developer", you can find ways to avoid the situation. in the end, the legacy repository ended up with those PRs that are waiting people to review and QA. It's not about serverless architecture. it's about code ownership and having a solid CI/CD work process. I suggested him to form a plan to do that. git-ops can be a candidate if it's well crafted with QA steps.
There might something I can help. And then I remembered OpenFaaS community is using Derek - a serverless 🤖 to manage PRs and issues. 
If we add more "pipe lines" that makes sense to the frontend team, then we can use it to improve our daily work process. Yes, I agree that it's more about people problem. but it will accelerate the plan. Now, I found a chance to use openfaas at work at last. Good thing about my situation is that our backend will be broken into services and we're going to use kafka as our message queue. And it's possible to launch openfaas function with kafka-connector. (you can trigger your functions via sns, rabbit mq and cloud events too) 
People will see it working and feel good about derek and automation for chores. If people start to add more features or functions then they might want to replicate the experience for production environment. we can do it with "stable" service like aws lambda in the beginning but it will cost money. then openfaas is a good option. isn't it?

Introducing OpenFaaS to the company

댓글