Harry B. hungbang

Coding Conventions

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.

80% of the time spent on a piece of software goes to maintenance.
Hardly any software is maintained for its whole life by the original author.
Code conventions improve the readability of the software, allowing engineers to understand new code more quickly and thoroughly.
If you ship your source code as a product, you need to make sure it is as well packaged and clean as any other product you create.

Preloading data in a redux application

A redux app is a chicken and egg problem. Given a particular state, the app should render a certain thing. But... where does that state come from?

Starting from empty

Given a blank state, the app needs to rely on the URL to fetch the right data to populate the state.

In a server-side app, the initial state is determined in exactly this way. Given the initial URL, populate the state, render the app, send it to the client.

In a client-side app the situation is exactly the same, except it's totally different. On the client you have way more contextual information than just the URL. Given the URL, the current app state, a components own props and its internal state... a component must decide which data it needs loaded.

Best efforts 1 Phase commit

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. 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.

Scenarios

Consider a jms based service, where there is an inbound Queue manager (QM1), an outbound queue manager (QM2) and a database (DB). Here are the scenarios that I would like to cover using Best efforts 1 PC commit process:

Happy path

Start MQ transaction on QM1 2

Ondrej Sika <[email protected]>

Database

Select Database

use DATABASE_NAME

Kubectl output options

Let's look at some basic kubectl output options.

Our intention is to list nodes (with their AWS InstanceId) and Pods (sorted by node).

We can start with:

kubectl get no

Master: Dependencies

apt update && apt upgrade -y
curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add -

cat <<EOF > /etc/apt/sources.list.d/kubernetes.list
deb http://apt.kubernetes.io/ kubernetes-xenial main
EOF

	# stop all processes
	docker stop $(docker ps -aq)

	# remove all containers
	docker rm $(docker ps -aq)

	# remove all images
	docker rmi $(docker images -aq)

	# delete all volumes

	/**
	* @license CC0 1.0 (http://creativecommons.org/publicdomain/zero/1.0/)
	*
	* The problem:
	* You need to make a cross-domain request for JSON data, but the remote
	* server doesn't send the necessary CORS headers, and it only supports
	* simple JSON-over-HTTP GET requests (no JSONP support).
	*
	* One possible solution:
	* Use 'jsonp-proxy-request-interceptor' to proxy the request through

	package ru.tkachenko.app.config;

	import com.fasterxml.jackson.databind.DeserializationFeature;
	import com.fasterxml.jackson.databind.ObjectMapper;
	import com.fasterxml.jackson.datatype.jsr310.JavaTimeModule;
	import lombok.RequiredArgsConstructor;
	import org.elasticsearch.client.Client;
	import org.elasticsearch.common.settings.Settings;
	import org.elasticsearch.common.transport.TransportAddress;
	import org.elasticsearch.transport.client.PreBuiltTransportClient;

	$ git push -f heroku release-20110606^{}:master

	# I don't know [tag]^{}