The following set of summaries are from the Kubecon and Cloud Native Con Europe in Denmark from 2-4 May 2018.
These summaries are from conference talks that I thought provided more interesting thinking points.
This is the list of talks provided in the reccent Gophercon Conference held in Singapore on 4th May 2018
Go with Versions Project-driven journey to learning Go Resilency in Distributed Systems Understanding Running Go Program Go for Grab Optimize for Correctness Build your own distributed database The Scandalous Sotry of Dreadful Code Written by the Best of Us Erlang for Go developers Go and the future of offices Reflections on Trusting Trust for Go The lost art of bondage Below are some of the more interesting points raised during the talk (View the full talk to understand the context on what and why a certain point was raised.)
View the full list of Fossasia Video recordings on the [engineers.sg] website on this website: https://engineers.sg/conference/fossasia-2018
Here are some of the videos I particularly liked. I summarized some of the interesting points from said websites.
Out of random curiousity and laziness on my part, I decided to create a CLI tool which would allow me to create tasks on task managements websites such as on Asana, and issues in Github/Bitbucket.
This is going to be a pretty short post but should prove to be useful if you are already familiar with tool.
Quick intro of normal website tracking # When one navigates through a normal server rendered website that is utilizing Google Tag Manager or Google Analytics (assuming that is is set up right), as the page loads, it would send a page view hit to the Google Analytics server. This is normal familiar behaviour for most people who used the tools.
This is an application based on a previous blog post on Bookcase application.
The link to the code base of the application:
https://github.com/hairizuanbinnoorazman/golang-web-gin-book-store
There is a chance that when you are on the code base, the application is not fully operational; I am still adding code to it to add functionality to the application
We would try to implement the various technology stack for some common web application scenario in several types of libraries. In our case here, we would attempt to implement it for the following scenario.
An excellent resource to read on Refactoring Golang code safely and to ensure that Golang code continue does not result in breaking changes in the codebase.
https://talks.golang.org/2016/refactor.article
An important to take away from the article is the fact that when making API changes to a code base, the portion that results in largest amount of work is the amount of code repair that needs to be done. Here are some of the examples to take note:
A list of conferences and meetups and exhibitions to look for especially in 2018:
This kind of personal list that I’m keeping track; it mainly revolves around Golang, modern architecture technologies e.g. Cloud technologies etc, Python and even R (One of my initial language, I still do keep a lookout of how it’s doing nowadays.)
After a long while being on some managed platform for writing blog posts, I decided to move out of that into one which would require myself to manage things on my own.
Disclaimer: There are definitely better ways of doing this; this is more of a lazy man’s way of doing it. This is just to explore the possibility of getting a golang application into AWS Lambda and successfully running it.
Full Playlist can be found here: https://www.youtube.com/watch?v=Z3aBWkNXnhw&list=PLj6h78yzYM2P-3-xqvmWaZbbI1sW-ulZb
Cloud Native Landscape: https://github.com/cncf/landscape
Keynote: Can 100 Million Developers Use Kubernetes? Kubernetes: This Job is Too Hard: Building New Tools, Patterns and Paradigms to Democratize Weaving the Service Mesh Microservices, Service Mesh, and CI/CD Pipelines: Making It All Work Together Developing Locally with Kubernetes State of Serverless Keynote: What’s Next? Getting Excited about Kubernetes in 2018 Keynote: Manage the App on Kubernetes Video References
Following from the previous blog post: Using AWS Lambda for Data Science Projects and Automations - Part 1
Let’s deploy a serverless application!
Problem Statement:
The application we would be trying out this time will do the following:
A thought experiment # Let’s say there was this one day during your usual work hours where you are tasked to handle some data transformations between your data sources. The data source is csv file generated from backend systems and is provided on the hourly basis. These data sources are to be analyzed as soon as possible and the insights are to be relayed to the marketing and business intelligence teams. How should we handle this? (Of course we should aim for as cheap a solution as possible)
I’ve been learning plenty of Golang nowadays and one of the most common design patterns that I keep hearing about is the decorator pattern. It is often used when handling with web requests; where you would create a function that accepts a struct that implements the handler interface which would then return an struct that also implements the handler interface.
A sample application to kind of get started with Go.
This application involves pinging a channel on Slack via a webhook. Slack provides a unique URL in order to ping Slack with messages from a script/application.
This is a suggestion piece and not a recommended way of using docker or anything.
Motivation # The question we would want to know here is how do we exactly run the full on/all the unit tests for our applications built via Docker. One way to do this is to rely on a build server like Jenkins to create the required environment which we would need for a build and then run the unit test needed. However, this would mean that there is need to bootstrap a environment to do so.
Over the weekend, I’ve been experimenting whether if its possible to set up screen recording on a linux server. This is partly just out of curiosity but also, a little a bit of frustration. Imagine if you were in a position where you aim to assist people in recording their training sessions over on Google Hangouts but in order to do so, you would need to be around and your computer needs to be “sacrificed” in order to do the recording.
While attempting to play around with object ids via the rgoogleslides package, the main issue I got was to quickly understand which object id referred to which element on the slide?