What Comes After Microservices? • Matt Ranney • YOW! 2016
HTML-код
- Опубликовано: 26 сен 2024
- This presentation was recorded at YOW! 2016. #GOTOcon #YOW
yowcon.com
Matt Ranney - Chief Systems Architect at Uber, Co-founder of Voxer
RESOURCES
/ mranney
mastodon.socia...
/ mranney
github.com/mra...
ABSTRACT
Matt Ranney talks about the limits that some companies have encountered in their large #microservices deployments and some non-microservices approaches to those same problems. He also talks about the non-microservices systems that Uber is building to maintain developer productivity with a large and growing engineering team. [...]
RECOMMENDED BOOKS
Sam Newman • Monolith to Microservices • amzn.to/2Nml96E
Sam Newman • Building Microservices • amzn.to/3dMPbOs
Ronnie Mitra & Irakli Nadareishvili • Microservices: Up and Running• amzn.to/3c4HmmL Mitra, Nadareishvili, McLarty & Amundsen • Microservice Architecture • amzn.to/3fVNAb0
Chris Richardson • Microservices Patterns • amzn.to/2SOnQ7h
Adam Bellemare • Building Event-Driven Microservices • amzn.to/3yoa7TZ
Dave Farley • Continuous Delivery Pipelines • amzn.to/3hjiE51
/ gotocon
/ goto-
/ goto_con
/ gotoconferences
#NonMicroservices #PostMicroservices #SoftwareArchitecture #SoftwareEngineering #Programming #MattRanney #YOWcon
Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at gotopia.tech
Sign up for updates and specials at gotopia.tech/n...
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
www.youtube.co...
What comes after implementing Microservices:
Pain!
We are currently releasing older YOW! videos to serve as a valuable archive, preserving historical content. It is possible that a video is perceived as outdated. We believe it offers insightful glimpses into the past, enriching our understanding of history and development.
Can you prepend the year, so we can see immediately it's almost 10 year old content.
Thanks for your input. We used to do it that way, but noticed that the talk title and especially the speaker name gets pushed out of sight, which is just as important to many viewers.
watched it at 1.5x - aged very well, unfortunately.
most of the talk is about problems with Microservices Uber encountered while change coupling is highlighted. Most of it should be familiar for interested devs of 2024.
The other part of the talk is about composabbility as a desired solution to takkle change coupling in my understanding.
Good takes on composabbility in synchronous Architecture. In my words, with the increase number of services cross cutting changes are a problem because most services may need to adapt to the new requirement. And cross cutting changes are quite common. Hence, some kind of solution is desirable where composabbility is facilitated like by intercepting flows without changing collaborating services.
I did not really get the desired direction - Based on the other topics he talked about I assume some kind of messaging based workflow coordination coupled with synchronous communication, I guess outgoing from the coordinator. Yet, the last slide suggested some kind of interception / interruption of a flow, I can't get my head around when the goal is not to change other services.
So, what comes next? There was no direct answer for architectures imho. And in 2024 I think my answer would be, whatever architecture works for the business requirements. I think the industry moved away from fully distributed or total monolithic architectures - so something in between.
Sounds like as of 2016, when this video came out, Uber had built themselves a distributed monolith to run its core functions. I would be really curious to see how things evolved and ended up in 2024.
I agree, but is that actually bad? I mean they continued to grow and scale whilst doing so. It seems like Netflix had a similar story.
Despite the purity of Event Driven Architecture, is it so costly in the early stage of development that it stifles innovation?
This is a great update from Matt, now at DoorDash:
ruclips.net/video/LcJKxPXYudE/видео.html
This was a great talk, especially given that we are now 8 years post and these topics are very much up for a successful company to figure out for themselves still.
It seems that in the RPC world, engineers are still thinking in an "in-process" style. That doesn't mean it's bad at all, but it just means that a function to retrieve "some thing" just returns the object they need. This mindset though, is the mindset of most web programmers (me included). For scaling up, it makes sense for engineers to continue thinking that an HTTP call to a service is just like calling a function. But I guess the point of this talk is that, in those scale up times, RPC continues to make the customers and engineers happy, but it's technical debt which will make the next change much more difficult.
What Comes After Microservices? - Common sense
> What Comes After Microservices?
The fashion for monolith will return under another name!
micro services are very slow, very expensive, resource intensive and take forever to add new features. Most developer's time is wasted doing nothing.
I'm a bit outdated developper, what's the current trendy architecture model please ? :)
@@vincentprince1833 monolithic microservices
Just monolith brother
Rest well
What comes after? Seems like something that should be in the title of this video. Not going to watch it.
Diddy was running microservices in his freak off mansion so my answer is jail. Jail comes after microservices.