Let's imagine you run a complex service or app, and you have to manage a backend solution that grows fast. You have to find a way to handle the releases cycle. It means taking care of restarting services, migrating databases, expiring caches, as well as notifying client's apps for the update. Now, add a new layer of complexity: to quickly try-and-fail, you also use a feature-flipping architecture that allows you to run tests on various client segments. Even for a limited amount of time. And, because your team is great, you deliver several times a day. To address all those needs, Node.js is a great candidate. Properly hooked behind a Git repository that will allow you to push your codebase and configs, we can conceive a modular system to manage your deployment process. Based on Streams and Functional Programming, we will present a global solution capable to deliver your codebase and reprocess its configuration on-the-fly. With a simple git push. Let's see what a modern, robust, and distributed deployment platform should look like.


Comments are closed.

Great sample about socket usage to communicate between git hooks and.
That are the kind of hack we need!!

Very interesting!

NodeJS, sockets and Git: what do you want more than that?!


Federico at 14:57 on 16 Nov 2018

I enjoyed the hooks part more than the feature one

Really interesting and give huge tips that surely I will investigate, but there was a lot of confusion inside my mind about the acl slides and git hooks jumping from a topic to another @_@

Simone Savino at 22:09 on 16 Nov 2018

Simple and useful

Marco Da Re at 00:04 on 17 Nov 2018

topic interesting, maybe too many GIF on slides :)

Nice talk very interesting the part of git hook but I need to deep inside the difference of this approach Vs a normal CI like tarvis or Jenkins

Filippo Nardi at 12:35 on 19 Nov 2018

Interesting use of Git and Node.js

everything explained in a good way

Interesting talk, but maybe too many things

Alberto Roli at 17:17 on 19 Nov 2018

A bit hard to follow

Nice talk, maybe too many things for the speech time.