Pragmatic approaches to the Event Horizon
•Télécharger en tant que PPTX, PDF•
2 j'aime•540 vues
The mission to μServices, should anyone choose to accept it, typically starts with a set of approaches and patterns around system design or deconstruction. The objective of these methods being to enable better isolation and autonomy for teams, data and processes. As the journey progresses, events typically appear as both a goal and an approach to enable even looser coupling and better scalability. In this talk Kingsley will share with you a rough overview of the eventing landscape and why events, immutable data, functions and processes are key to developing scalable services. Concretely, pub/sub, event sourcing and event storming will be covered as well as experiences from building event based services and frameworks. There will also be suggestions on where microservices are heading, and the close proximity between MuServices and blockchain technology. The talk will be both introductory and interactive, with life vests and support provided. See: https://skillsmatter.com/skillscasts/10730-looking-forward-to-kingsley-davies-talk
Recommandé
Recommandé
Contenu connexe
Similaire à Pragmatic approaches to the Event Horizon
Similaire à Pragmatic approaches to the Event Horizon (20)
Dernier
Dernier (20)
Pragmatic approaches to the Event Horizon
- 2. Pragmatic approaches to the Event Horizon Kingsley Davies @kings13y
- 3. kings13y https://github.com/Tesco/mewbase [ { "eventId": "intro", "eventType": "research-developer", "data": { "industry": "gaming" , "duration": "1" }, { "eventId": "arch", "eventType": "monolith-decomposer", "data": { "industry": "gaming" , "duration": "4" }, { "eventId": "dev", "eventType": "es-builder", "data": { "industry": "govt" , "duration": "1" }, { "eventId": "foss", "eventType": "es-fwk-builder", "data": { "industry": "retail" , "duration": "0.5" } ]
- 4. Overview - Changing perspective ● Past ● Present ● Future
- 6. Classic: As-is / To-Be Data Store Client Service Tier Client Product Service Wallet PrefsAccount DS1 DS2 DS3
- 8. Events, Events, Events ● Data architecture ● Model of interaction A way of life…
- 9. First taste of events Pub [event-emitted]
- 11. Event Storming
- 13. Storing Data
- 14. Storing Facts (Event Sourcing) http://bit.ly/2hfqssi
- 15. Reading Facts
- 18. FP and Microservices Immutability Composability Functions as 1st class citizens Laziness => Event Source storage => Functions over data; Service chains => Refinement services, Bounds => Serverless
- 19. When things go silent/bang
- 20. Checkpoint ● Event Storming ● Immutable journal of events ● State and Reads as a leftFold on events ● Build for failure
- 21. Anything else familiar from checkpoint ? ● Immutable journal of events ● State and Reads as a leftFold on events ...from serverless to masterless ? …….and trustless (anonymous) ?
- 22. Conclusions X-Domain (product) Storming + Domain Teams Inversion of Flow => Innovation Broken promises, retained dreams Events + Functions DDD, Dist Sys, Ops & Crypto
- 23. Thanks, Links and Questions THANK YOU!!! ● @kings13y / @underscore ● http://underscore.io/ ● http://breakpointradio.net ● https://github.com/Tesco/mewbase ● https://www.youtube.com/watch?v=ycxvm OKDHMQ ● https://www.youtube.com/watch?v=gTLV HrMxBww ● https://t.co/GJIIuBeNu5 ● https://vimeo.com/223982152 ● https://t.co/FGhs4wwzvF ● https://youtu.be/FJ3T8ytF6ro ● https://www.youtube.com/watch?v=JHGk aShoyNs
Notes de l'éditeur
- Contact details: Twitter: @kings13y Email: kingsley@underscore.io Underscore are a UK based consulting company specialising in training, development and delivery of all things FP (esp Scala), Microservice design, build and support. Holla at me if you want support on a journey to MuServices or Event based services! https://underscore.io/
- OVERVIEW Past Where and why for microservices Present Current state of play What, How and Why Future Indicators from the direction of travel WHAT DO ATTENDEES WANT FROM THE DAY ?
- ONE DOES NOT SIMPLY MOVE TO MUSERVICES Deploy, monitor, eventual consistency, interfaces blah.. DRIVEN BY SUPPORTING ECOSYSTEM SCALE WORK; DEPLOY; TEAMS; COGNITIVE LOAD microservice really allow us to optimise up the weakest relationship which is the cognitive one (Cockroft sic) X-FUNCTIONAL TEAMS…. TO A POINT
- DUAL - NOUNS and EVENTS PUSH Data processing PULL Freedom Both Supporting technologies (Kafka, Nats.io) Postel’s Law++ (more on that later)
- What are events ? FACTS and IMMUTABLE PAST TENSE (ideally) async - Promises ?
- Events always start at the PUB… P2P (e.g. frameworks), pub/sub… Missing/dropped events How to deal with this..
- EXTERNAL INPUT -> COMMAND -> EVENT Commands: PRESENT TENSE ...also readmodel
- Lead by business… using the language of the business Cluster of notes on problem areas
- Locks and writes Loses context of change Typically couples Write and Read storage COULD HAVE A table that mutates and an audit table (updated by triggers) from it.. - each update saves a copy of entire row - need to figure out the change - not always reliable (what is a trigger gets dropped) - no correlation to what lead to the change.
- - partition system by aggregates (which are ordered) e.g. by user - guaranteed order within an aggregate - talked about dropped events earlier.. http://kappa-architecture.com/
- - polyglot persistence for reads - snapshots and memento patterns - projections
- Ask ppl for input! Autonomy => moving faster; looser coupling - Postel++ (from data/space to time) Traceability => regulation Stability => Inversion of control, upgrades Postel’s law: Be conservative in what you send, be liberal in what you accept
- Monitoring key Ability to delay / replay events Promise theory and build for chaos and resilience http://shop.oreilly.com/product/0636920036289.do
- Product as (event) architecture Still with ops teams as a function of procurement/budget management