Microservices from the Trenches • Sander Hoogendoorn • GOTO 2022

This presentation was recorded at GOTO Amsterdam 2022. #GOTOcon #GOTOams

ORIGINAL TALK TITLE
Microservices from the Trenches: Concepts, Design, Architecture, Code, Testing

ABSTRACT
A practical guide to the many architectural, design, and coding decisions you too will need to make on the way to microservices.

To further improve time-to-market and adaptability in delivering their services, e-commerce company iBOOD (well-known for their daily deals) is reshaping their software landscape, which largely consists of a number of mobile applications (built with Flutter), web applications (TypeScript, #React), and back-end services (#TypeScript, #Nodejs, #Python, #Kotlin).

TIMECODES
00:00 Intro
01:09 Microservices architecture
02:29 Agenda
04:07 Introduction
05:43 Lessons learned
18:00 Architecture
23:25 Domain
32:22 Data
35:49 Continuous delivery
42:42 Retrospective
45:32 Outro

Read the full abstract here:

RECOMMENDED BOOKS

#Microservices #Programming #MicroservicesArchitecture #SoftwareArchitecture #MonolithToMicroservices #iBOOD #SanderHoogendoorn #BuildingMicroservices #ContinuousDelivery #CICD

CHANNEL MEMBERSHIP BONUS
Join this channel to get early access to videos & other perks:

Looking for a unique learning experience?

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.

[GOTO-]

Looking for books & other references mentioned in this video?
Check out the video description for all the links!

Want early access to videos & exclusive perks?

Question for you: What’s your biggest takeaway from this video? Let us know in the comments! ⬇

[sweetphilly]

feel like this needs a bit of an audio boost or something. great talk though

[blipojones]

The theme with so many of these talk is people prefering to apply patterns before THINKING and visualising the problem (assuming they have even defined it at all).
Example, so many engineers "DRY" everything for no reason, example here, the speaker mentions the services having a similar strucuture and that being OK, another engineer would see that as a thing to '"DRY"/abstract. Wether it microservices, or monorepos, right down to small language features, these developers will do the same thing i.e. apply all the patterns in not just the right places, but also allll the wrong places to the detriment of the business focus or the problem being solved.

[TrvGuY]

I agree with 95% of what he says, but aggregates = microservices sounds like entity services to me, which produces high coupling between services.