When unsing docker compose you can have a problem with the order of dependent linked containers
The solution is to start a script which tries to access a service and waits until it gets ready before loading your program
// Use Gists to store code you would like to remember later on | |
console.log(window); // log the "window" object to the console |
When unsing docker compose you can have a problem with the order of dependent linked containers
The solution is to start a script which tries to access a service and waits until it gets ready before loading your program
diff --git a/compiler/cpp/src/thrifty.yy b/compiler/cpp/src/thrifty.yy | |
--- a/compiler/cpp/src/thrifty.yy | |
+++ b/compiler/cpp/src/thrifty.yy | |
@@ -653,7 +653,7 @@ | |
$$ = new t_const_value(); | |
$$->set_integer($1); | |
if (!g_allow_64bit_consts && ($1 < INT32_MIN || $1 > INT32_MAX)) { | |
- pwarning(1, "64-bit constant \"%"PRIi64"\" may not work in all languages.\n", $1); | |
+ pwarning(1, "64-bit constant \"%" PRIi64"\" may not work in all languages.\n", $1); | |
} |
Latency Comparison Numbers | |
-------------------------- | |
L1 cache reference 0.5 ns | |
Branch mispredict 5 ns | |
L2 cache reference 7 ns 14x L1 cache | |
Mutex lock/unlock 25 ns | |
Main memory reference 100 ns 20x L2 cache, 200x L1 cache | |
Compress 1K bytes with Zippy 3,000 ns 3 us | |
Send 1K bytes over 1 Gbps network 10,000 ns 10 us | |
Read 4K randomly from SSD* 150,000 ns 150 us ~1GB/sec SSD |
Once upon a time…
I once took notes (almost sentence by sentence with not much editing) about the architectural design concepts - Command and Query Responsibility Segregation (CQRS) and Event Sourcing (ES) - from a presentation of Greg Young and published it as a gist (with the times when a given sentence was heard).
I then found other summaries of the talk and the gist has since been growing up. See the revisions to know the changes and where they came from (aka the sources).
It seems inevitable to throw Domain Driven Design (DDD) in to the mix.
Listing pods with kubectl get pods
, then select a pod name and copy paste it into kubectl logs [pod name]