Refactor talks, add day2

4 files changed, 47 insertions, 0 deletions

diff --git a/first-talk.txt b/day1/first-talk.txt
index ffd2f65..ffd2f65 100644
--- a/first-talk.txt
+++ b/day1/first-talk.txt
diff --git a/day1/no-sql.txt b/day1/no-sql.txt
new file mode 100644
index 0000000..5ce9723
--- /dev/null
+++ b/day1/no-sql.txt
@@ -0,0 +1,5 @@
+https://redis.io/commands/sadd
+https://www.postgresql.org/docs/9.1/hstore.html
+https://wiki.openstreetmap.org/wiki/PostgreSQL
+https://en.m.wikipedia.org/wiki/Benford%27s_law
+https://php-ml.readthedocs.io/en/latest/machine-learning/workflow/pipeline/
diff --git a/second-talk-microservices.txt b/day1/second-talk.txt
index 46df43f..46df43f 100644
--- a/second-talk-microservices.txt
+++ b/day1/second-talk.txt
diff --git a/day2/first-talk.txt b/day2/first-talk.txt
new file mode 100644
index 0000000..1cb53b3
--- /dev/null
+++ b/day2/first-talk.txt
@@ -0,0 +1,42 @@
+Microservices gone wrong
+
+- starting from scratch
+
+api gateway
+middleware for extrenal requests
+message-bus rabbitMQ
+
+Service oer domain entity
+
+Meta service using ES
+Kurbenetes
+
+Why local dev failed?
+Slow.
+Incosistent
+Would break
+
+mainly: "Someone elses problem" - all devs
+
+
+Production release took 1 week
+Cost of context switching
+
+Smoke Test
+
+- Lessons Learned
+
+    - service call's are unreliable
+    - "microlyth"
+
+1. DOnt do micorservices
+    a. unless you have a dedicated tooling and automation team
+2. Start with big services
+    a/ Split if you require
+3. Auomate everything
+    a spin up, deployment migration, backup state resortation Elliptic
+4. Dont plan for failure, live it
+    a. failure modes should bebuilt first, tested first, and relied upon
+5. Define SLO early
+    a. Define business objectives for each service and system before building
+