Daily

Kubernetes powers our #backend services as it is very easy in terms of #devops (the managed version). We deploy everything using @helm charts as it provides us to manage deployments the same way we manage our code on GitHub . On every commit a CircleCI job is triggered to run the tests, build Docker images and deploy them to the registry. Finally on every master commit CircleCI also deploys the relevant service using Helm chart to our Kubernetes cluster

For developing our @{#frontend}|topic:null| applications, we decided to use Vue.js . Being such an easy to learn library, compared to React for example, it made everything so easy. At first we started with Polymer but the existing tooling and small community at the time made us look for alternatives.

As far as the backend goes, we first had to decide which database will power most of Daily services. Considering relational databases vs document datbases, we decided that the relational model is a better fit for Daily as we have a lot of connections between the different entities. At the time MySQL was the only service available on Google Cloud SQL so this was out choice. In terms of @{#backend}|topic:null| development Node.js powers most of our services, thanks to its amazing ecosystem there are a lot of modules publicly available to shorten the development time. Go is for the light services which are all about performance and delivering quickly the response, such as our redirector service.

I was thinking what could be the best option for deploying Daily's @{#frontend}|topic:null| applications. On one side there is Netlify , promoting and encouraging the JAM stack, very easy to deploy and manage your deployments. And on the other side, Kubernetes , specifically Google Kubernetes Engine as I don't like to manage my own clusters. Kubernetes provides much more options, in terms of deployment strategy, networking, etc but requires far more configurations. As I don't have any SSR on my applications, I decided that the ease of use of Netlify is the number one priority for the project.