My write up on @qconlondon #qconlondon Day 1:
evernote.com/l/AfIOuTmNA05J…
Highlights were @agupta03's talk about getting the @LinkedIn real-time distribution platform to scale to 1M likes/s.
Also @doodlesmt's talk about @lyft's approach to training ML models with streaming data
evernote.com/l/AfIOuTmNA05J…
Highlights were @agupta03's talk about getting the @LinkedIn real-time distribution platform to scale to 1M likes/s.
Also @doodlesmt's talk about @lyft's approach to training ML models with streaming data
Day 2 write up @qconlondon #qconlondon: evernote.com/l/AfJxpD9oGzhA…
Great day, with lots of highlights: @anjuan framing leadership lessons with inspiring stories about the Underground Railroad,
@lucamezzalira with lots of practical microfrontend advice...
Great day, with lots of highlights: @anjuan framing leadership lessons with inspiring stories about the Underground Railroad,
@lucamezzalira with lots of practical microfrontend advice...
...@percy_link and @breckcs talk about how the
@Tesla Virtual Power Plant is able to make energy grids more efficient, also great advice about how to approach distributed systems at scale,
and @msmichellegar's journey from BFFs to centring the organisation's data around GraphQL
@Tesla Virtual Power Plant is able to make energy grids more efficient, also great advice about how to approach distributed systems at scale,
and @msmichellegar's journey from BFFs to centring the organisation's data around GraphQL
Day 3 write up @qconlondon #qconlondon: evernote.com/l/AfLiWzBj67FA…
Very interesting to compare the talk about @StarlingBank with @monzo...
Very interesting to compare the talk about @StarlingBank with @monzo...
@dtpo and @martin_dow from @StarlingBank talked about their FRP approach to Starling's 30 services which can all be run from a single laptop.
@mattheath and @suhailpatel from @monzo told of how they develop and manage Monzo's 1600 microservices written in @golang...
@mattheath and @suhailpatel from @monzo told of how they develop and manage Monzo's 1600 microservices written in @golang...
...the similarities were most interesting: standardised, homogeneous services optimised for understandability.
