Skip to content

Latest commit

 

History

History
543 lines (456 loc) · 19.2 KB

README.md

File metadata and controls

543 lines (456 loc) · 19.2 KB

Goto 2018

Table of Contents

Created by gh-md-toc

Key Learnings

Troubleshooting & Debugging Microservices in Kubernetes

https://cloud.google.com/stackdriver

Namespace ~ Environment

kubectl get ns
kubectl get pods -n abcd

Alles gleich - Unterschiede, zb DB secrets: in config map

Logs durchsuchen: BigQuery

kubectl proxy
kubectl exec ...
kubectl port-forward ...

weave-scope

* [Stackdriver Trace](https://cloud.google.com/trace/)
* [Stackdriver Debugger](https://cloud.google.com/debugger/)

Debugger: snapshot

Tracing: open senses, zipkin

Serverless Architectural Patterns and Best Practices

  • Avoid host afinity

  • Consul, eureka, zookeeper

  • SAM

  • don't dos from the talk:

    • Struktur unklar, keine klare Abgrenzung der Themen
    • Top-Level view fehlt, viele vollkommen willkürlich wirkende Details ...
    • Warum das ganze? Welche >Anwendungsfall<? Wozu hilft das?
    • Begriffe nicht erklärt
    • Wozu sind die Produkte da?
    • Werbeveranstaltung
    • Total überfrachtet => einfache Diagramme
    • Langweilig, >keine Demos<
    • Zu viel Text, zu wenig Diagramme

  • AWS

    • Komplexe, eigene Welt
    • Will man sich das antun?
    • Spart einem das Arbeit?
    • Vendor lock

Augmented Reality - Flavours, Challenges and Writing AR Experiences in JavaScript

Your Superpower User Manual

How Software can be Thought of as a Force for Good

Energy and Education Access for Remote Communities

  • BBC Breakthrough
  • BBC Power to Himalaya
  • Inter & Intravillage Communication

Experience Report - Teaching Kids to Code for 10 Years

Insecure Transit - Microservice

metdata

content

Swearing, Nudity and Other Vulnerable Positions

metadata

cotent

Google Aristotle

  • psychological safety - feel safe to take risks and be vulnerable
  • dependability - get things done with quality
  • Structure & Clarity - clear roles, plans, Goals
  • Meaning - work is personally important
  • Impact - people think works matters, feel small wins
  1. Psychological safety: Can we take risks on this team without feeling insecure or embarrassed?
  2. Dependability: Can we count on each other to do high quality work on time?
  3. Structure & clarity: Are goals, roles, and execution plans on our team clear?
  4. Meaning of work: Are we working on something that is personally important for each of us?
  5. Impact of work: Do we fundamentally believe that the work we’re doing matters?

-> checklists

Psychological safety: belief that one will not be punished or humiliated for speaking up with ideas, questions, concern or mistakes

  • or: "You're safe, when you can speak your truth, raise your concerns and give and receive constructive feedback without the fear of humiliation, rejection or punishment"

  • Mindfulness

    • Paying attention is about noticing how you feeld, how people around you are feeling and approaching people and the organisation with curiosity and not judgement.

improv

wisenoodles.com

-> "yes, and" instead of "yes, but" -> go with the idea, improvise, leave room for creativity

  • Unsafety -> stress -> inpact on social life

Are you OK? -> replace judgent with curiosity

Optimizing Kubernetes deployments with Helm

metadata

content

examples

helm install stable/sonarqube --namespace sonarqube --set service.externalPort=9001
helm update ...
helm history ...
helm rollback ...
-f "values.prod.yml"
--set ...=....
--set-file
--dry-run --debug
helm create --starter
helm test

Artificial Intelligence Reloaded - AI Applications in the Industry

metadata

content

  • Big data is foundation of AI
  • word2Vec
  • LSTM
  • DVC

Event-based Architecture and Implementations with Kafka and Atom

metadata

content

The Simpsons and Their Mathematical Secrets

Frugal Innovation

metadata

content

  • Frugal innovation: Book Jugaad Innovation
  • Constrainted Contexts
  • Design Thinking

The 7 quests of resilient software design

metadata

content

  • Understand busines case
  • Resilience is not about making money - Resilience is about not losing money
  • Use business monitoring
    • all business decisions are made in the gut
    • pretend to adress the brain, but aim for the gut
    • "Its strange for developers, but it's the way managers work"
  • Deal with unavailability
    • Think about when a problem occurs
  • Failures:
    • Crash failure
    • Omission failure
    • Timing failure
    • Response failure
    • Byzantine failure
    • distributed Systems
  • non-determinism
    • we usually use deterministic thinking to reason about distributed systems
    • Distributed systems introduce non-determinism regarding
      • Execution completeness
      • Message ordering
      • Communication timing
    • You will be affected by this at the application level
      • Don’t expect your infrastructure to hide all effects from you
      • Better have a plan to detect and recover from inconsistencie
  • Availability goes down with the number of services involved in a request
    • Assume a service availability of 99,5% (incl. planned downtimes)
      • 10 services involved in a request à 95,1% probability of success
      • 50 services involved in a request à 77,8% probability of success
  • Establish the ops-dev feedback loop
  • Site Reliability Engineering (STE)
  • Everything we learned about reuse is good inside boundaries, but outside these it makes systems instable
    • => get the functional design right
  • Be (extremely) wary of reusability
    • Reusability increases coupling
    • Reusability usually leads to bad service design
    • Reusability compromises availability
    • Reusability rarely pays
    • Do not strive for reusable services
    • Strive for replaceable services instead
    • Try to tackle reusability issues with libraries
  • Mitigate
  • Using resilience patterns
    • Patterns are options, not obligations
    • Don’t pick too many patterns
    • Each pattern increases complexity
    • Complexity is the enemy of robustness
    • Each pattern costs money in dev & ops
    • You only have a limited resilience budget
    • Look for complementary patterns
  • caching won't always help
  • Preserve the collective memory / Use wisdom from earlier

Accelerated Learning: How Agile Can Help You?

metadata

content

  • comfort zone
  1. DECIDE WHAT YOU WANT
  2. DECONSTRUCT THE SKILL
  3. RESEARCH THE SKILL JUST ENOUGH
  4. REMOVE BARRIERS
  5. PRECOMMIT TO PRACTICE AT LEAST 20 HOURS
  • Reading / watching recos:
    • Expert in a year
    • First year guitar progress jack woodman
    • Therese trollbu
    • The Dan Plan
    • The tim ferris experiment
    • Andrew Tarvin - Humor at Work <-
    • How to learn anything in half time jim kwik
  • learning tips:
    • Find menote
    • Book
    • Youtube
    • Record yourself
    • Get rewards

The World after Microservice Migration with Service Mesh and Contract Testing

metadata

content

The Leprechauns of Software Engineering

metadata

content

GraalVM: Run Programs Faster Anywhere

metadata

content