Skip to content
View hungbang's full-sized avatar
🏠
Working from home
🏠
Working from home
Block or Report

Block or report hungbang

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned Loading

  1. java-best-practice java-best-practice Public

    1

  2. Java Coding Conventions Java Coding Conventions
    1
    Coding Conventions
    2
    ==============
    3
    
                  
    4
    This file will cover important coding practices that are important to stress when coding this program. Listed below are some of the more important details that should be stressed. Each programmer has his/her own way to deliver code. The importance of having similar coding conventions throughout this program are listed below.
    5
    
                  
  3. Stop all docker processes, remove al... Stop all docker processes, remove all containers, remove all images
    1
    # stop all processes
    2
    docker stop $(docker ps -aq)
    3
    
                  
    4
    # remove all containers
    5
    docker rm $(docker ps -aq)
  4. Best efforts 1Phase Commit using Spr... Best efforts 1Phase Commit using Spring chained transaction managemer and Apache Camel
    1
    # Best efforts 1 Phase commit
    2
    This is a non-XA pattern that involves a synchronized single-phase commit of a number of resources. Because the 2PC is not used, it can never be as safe as an XA transaction, but is often good enough if the participants are aware of the compromises.
    3
    The basic idea is to delay the commit of all resources as late as possible in a transaction so that the only thing that can go wrong is an infrastructure failure (not a business-processing error). Systems that rely on Best Efforts 1PC reason that infrastructure failures are rare enough that they can afford to take the risk in return for higher throughput. If business-processing services are also designed to be idempotent, then little can go wrong in practice.
    4
    
                  
    5
    # Scenarios
  5. Playing with kubectl output Playing with kubectl output
    1
    # Kubectl output options
    2
    
                  
    3
    Let's look at some basic kubectl output options. 
    4
    
                  
    5
    Our intention is to list nodes (with their AWS InstanceId) and Pods (sorted by node).
  6. Git Best Practices Git Best Practices
    1
    # Git Best Practices
    2
    
                  
    3
    This is a fairly common question, and there isn't a One True Answer,
    4
    but still, this represents a consensus from #git
    5