Clivern

Kubernetes Services in a Nutshell

By clivern On June 10, 2020 In Cloud Native, Kubernetes with 0 Comment

Service is a resource you create to make a single, constant point of entry to a group of pods providing the same service. Each service has an IP address and port that never change while the service exists. Clients can open connections to that IP and port, and those connections are then routed to one of the pods backing that service. This way, clients of a service don’t need to know the location of individual pods providing the service, allowing those pods to be moved around the cluster at any time.

Adding a Unique Request ID to Each Request in Django

By clivern On May 27, 2020 In Django, Python with 0 Comment

You can do that in Django using a middleware. The middleware needs to generate a unique request id (e.g. using UUID) and associate that id with the request.

Leader Election with Consul and Golang

By clivern On June 16, 2019 In Consul, Golang, Microservices with 0 Comment

Leader election is the process of designating a single node as the organizer of some task distributed among several nodes. The leader will be responsible for managing the others and coordinate the actions performed by other nodes. If for any reason the leader fails, other nodes will elect another leader and so on. This can help to ensure that nodes don’t conflict with each other.

Introducing Hippo: A Golang Microservices Toolkit

By clivern On June 4, 2019 In Golang, Microservices, Scaling with 0 Comment

It all began when I started to build some web services in golang. and everytime I have to create the whole architecture from scratch than solving whatever problem I was trying to solve.

Leveraging Consul’s DNS Interface

By clivern On May 8, 2019 In Scaling, Service Discovery with 0 Comment

Consul DNS interface allows applications to make use of service discovery without any integration with Consul. For example, instead of making HTTP API requests to Consul, a host can use the DNS server directly via name lookups like clivern.service.us.consul.

Django Custom Month and Year Lookup

By clivern On April 27, 2019 In Django, MySQL, Python with 0 Comment

Everyone want to keep Django timezone support but sometimes you need to keep your SQL queries a way from timezone conversion especially if by default your application timezone is UTC. Django will do something like this CONVERT_TZ(`app_incident`.`datetime`, 'UTC', 'UTC')) and it will return Null if the timezone table is empty. Even that conversion is not even needed.