diff options
Diffstat (limited to 'day2')
| -rw-r--r-- | day2/building-first-class-rest-apis.txt (renamed from day2/rest-apis.txt) | 7 | ||||
| -rw-r--r-- | day2/from-dev-to-prod-with-gitlab-ci.txt (renamed from day2/gitlab.txt) | 12 | ||||
| -rw-r--r-- | day2/microservices-gone-wrong.txt (renamed from day2/first-talk.txt) | 23 | ||||
| -rw-r--r-- | day2/more-secrets-of-crpyto.txt (renamed from day2/second-crypto.txt) | 12 |
4 files changed, 31 insertions, 23 deletions
diff --git a/day2/rest-apis.txt b/day2/building-first-class-rest-apis.txt index a087a52..681b818 100644 --- a/day2/rest-apis.txt +++ b/day2/building-first-class-rest-apis.txt @@ -2,6 +2,7 @@ ## Who - @michaelcullumuk +- Michael Cullum - Works for bud. (2 weeks ago) - core team at syfony - fig working group @@ -82,7 +83,7 @@ getErrors() handles error once in one function, included for all controllers - instead try and persist an object, throw new exception ## Output - - Symfony serializer component + - Symfony serialiser component - Choose output types easily - Transformers to migrate the data from an entity and map to response data - Allows us to focus on API respires not database layer entities @@ -123,10 +124,10 @@ getErrors() handles error once in one function, included for all controllers # RECAP PRINCIPLES OF REST USE HTTP WELL - verbs and codes -ERROR handling, abstracting validation. Handle expections for response codes +ERROR handling, abstracting validation. Handle expectations for response codes DTOs and param convertor Validation bubbles, catch and re-throw -Fromatting output wiht transformes +Formatting output with transforms Pagination - annoying but easy, if we p[ass via repos. Sorts and filters similar to Pagination Tools!!! Use em.] diff --git a/day2/gitlab.txt b/day2/from-dev-to-prod-with-gitlab-ci.txt index 2ce3906..f7e25ba 100644 --- a/day2/gitlab.txt +++ b/day2/from-dev-to-prod-with-gitlab-ci.txt @@ -1,5 +1,8 @@ # Dev to prod with GitLab CI +https://talks.bitexpert.de/phpuk19-gitlabci/ +Stephan Hockdorfer + ## Overview - Stefan - bitExpert AG (Germany) @@ -105,16 +108,17 @@ env first and then manually kick off the deployment for production ## Questions -Create a stadard web app +Create a standard web app Can Import from github!!! -Autoi dev ops? +Auto dev ops? - Auto turned on - Not sure how good it is - maybe we just disable Can we lock down how things get deployed - - ROle based auth is bad - - Dont have fine grain control (most of the team need nainainer role) + - Role based auth is bad + - Don't have fine grain control (most of the team need maintainer role) # Useful links https://www.sonatype.com/ https://traefik.io/ +https://talks.bitexpert.de/phpuk19-gitlabci/ diff --git a/day2/first-talk.txt b/day2/microservices-gone-wrong.txt index 1cb53b3..88a5096 100644 --- a/day2/first-talk.txt +++ b/day2/microservices-gone-wrong.txt @@ -1,24 +1,26 @@ -Microservices gone wrong +# Microservices gone wrong + +Anthony Ferrara +https://docs.google.com/presentation/d/1Ogejf47b7k0RWU-7lE_uBsCmJxL3CvydOl8fVukuQ_4/edit - starting from scratch api gateway -middleware for extrenal requests +middleware for external requests message-bus rabbitMQ -Service oer domain entity +Service per domain entity Meta service using ES Kurbenetes Why local dev failed? Slow. -Incosistent +Inconsistent Would break mainly: "Someone elses problem" - all devs - Production release took 1 week Cost of context switching @@ -29,14 +31,13 @@ Smoke Test - service call's are unreliable - "microlyth" -1. DOnt do micorservices +1. Don't 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 +3. Automate everything + a spin up, deployment migration, backup state restoration Elliptic +4. Don't plan for failure, live it + a. failure modes should rebuilt first, tested first, and relied upon 5. Define SLO early a. Define business objectives for each service and system before building - diff --git a/day2/second-crypto.txt b/day2/more-secrets-of-crpyto.txt index 18d5324..0246a58 100644 --- a/day2/second-crypto.txt +++ b/day2/more-secrets-of-crpyto.txt @@ -1,4 +1,7 @@ # Crypto +Christopher Riley +@giveupalready +https://github.com/carnage ## Overview: Why do we need crypto? @@ -8,13 +11,13 @@ Why do we need crypto? - Identity - Authentication -## Asymetric Cryto +## Asymmetric Crypto - Symmetric crypto faster, asymmetric slower and computational expensive - RSA - slightly old - Needs 2048+ size keys -## eliptic curve crypto +## Elliptic curve crypto - Dot function - Key exchange with shared key created from a -> aG -> aGb <- bG <- b - Week to man in the middle @@ -37,11 +40,10 @@ Why do we need crypto? - good for static data - hash tree -## BLock chain +## Block chain - Use block chain to share trusted messages -@giveupalready -https://github.com/carnage + |