e-budur

https://www.ntv.com.tr/gundem.rss
https://www.ntv.com.tr/dunya-kupasi-2018.rss
https://www.ntv.com.tr/turkiye.rss
https://www.ntv.com.tr/dunya.rss
https://www.ntv.com.tr/ekonomi.rss
https://www.ntv.com.tr/spor.rss
https://www.ntv.com.tr/teknoloji.rss
https://www.ntv.com.tr/yasam.rss
https://www.ntv.com.tr/seyahat.rss
https://www.ntv.com.tr/saglik.rss

posener

Why I Recommend to Avoid Using the go-kit Library

There is a trending 'microservice' library called go-kit. I've been using the go-kit library for a while now. The library provide a lot of convenience integrations that you might need in your service: with service discovery with Consul, distributed tracing with Zipkin, for example, and nice logic utilities such as round robin client side load balancing, and circuit breaking. It is also providing a way to implement communication layer, with support of RPC and REST.

iamphill

package main

import (
	"net/http"
	"Regexp"
)

type route struct {
    pattern *regexp.Regexp
    handler http.Handler

CristinaSolana

1. Clone your fork:

git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream