| #!/bin/bash | |
| # | |
| # tomcat7 This shell script takes care of starting and stopping Tomcat | |
| # | |
| # chkconfig: - 80 20 | |
| # | |
| ### BEGIN INIT INFO | |
| # Provides: tomcat7 | |
| # Required-Start: $network $syslog | |
| # Required-Stop: $network $syslog |
| http://m.lenta.ru/articles/2013/10/04/history/ | |
| http://m.lenta.ru/articles/2013/10/11/hyperborea/ | |
| http://m.lenta.ru/articles/2013/10/21/nevsky/ | |
| http://m.lenta.ru/articles/2013/10/28/tatar/ | |
| http://m.lenta.ru/articles/2013/11/04/ivan/ | |
| http://m.lenta.ru/articles/2013/11/11/timeoftroubles/ | |
| http://m.lenta.ru/articles/2013/11/15/ukraine/ | |
| http://m.lenta.ru/articles/2013/11/25/foreigners/ | |
| http://m.lenta.ru/articles/2013/12/02/petrone/ | |
| http://m.lenta.ru/articles/2013/12/09/czarinas/ |
A curated list of AWS resources to prepare for the AWS Certifications
A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.
Index:
I hereby claim:
To claim this, I am signing this object:
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real
| apiVersion: apps/v1beta1 | |
| kind: Deployment | |
| metadata: | |
| name: web-v1 | |
| namespace: default | |
| spec: | |
| replicas: 1 | |
| template: | |
| metadata: | |
| labels: |
| --- | |
| apiVersion: networking.istio.io/v1alpha3 | |
| kind: Gateway | |
| metadata: | |
| name: website-gateway | |
| spec: | |
| selector: | |
| # Which pods we want to expose as Istio router | |
| # This label points to the default one installed from file istio-demo.yaml | |
| istio: ingressgateway |
| --- | |
| apiVersion: networking.istio.io/v1alpha3 | |
| kind: Gateway | |
| metadata: | |
| name: website-gateway | |
| spec: | |
| selector: | |
| # Which pods we want to expose as Istio router | |
| # This label points to the default one installed from file istio-demo.yaml | |
| istio: ingressgateway |
| Latency Comparison Numbers (~2012) | |
| ---------------------------------- | |
| 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 |
| #!/usr/bin/env bash | |
| set -e | |
| # Helper script to automatically taint/untaint node based on CNI condition. | |
| # Used as a lifecycle hook for CNI Deployment. | |
| # Tainting helps to prevent FailedCreatePodSandbox issue caused by long CNI Plugin startup/restart | |
| # when there are pods scheduled on the nodes which doesn't have IP addresses assigned yet. | |
| # Expected environment variables: | |
| # MY_NODE_NAME - Name of the node. |
