@@duongdeptraiqua If walking around at 1km per hour generates this amount of sweat, I think it's safe to say there's something not 100% right :-D It was a great great talk though.
when her taking the order better showcased missing asynchronicity while the frying was just lack of parallel threads .... thinking about it, both do not hit the aynchronous feature of asynchronicity I would describe as "stop waiting" or "just react".
More than anything AWS specific, I enjoyed Dr. Werner Vogel's thought process and big-picture thinking. As a former ecologist, I was delighted by his connections of the natural world to concepts such as asynchrony, loosely coupled vs tightly coupled systems, and that individuals must evolve or die. The fact that his ideas outshown any AWS specifics when I'm a AWS fan and happily use it at work, is perhaps a testiment to him being a great thinker and presenter.
That's an interesting thing. What Werner is talking about requires alignment across EA, Solution and Software Architect roles (or depending on the size of your company, that might be CTO/Architecture/tech lead, or Head of tech/Senior Engineers and Junior Engineers). It also depends on whether you are green fields or legacy as well. There are often many more things to resolve. Just doing a straight pivot to a new way of working may be beyond the financial capacity of your business to realise, or not align with the targets the product team need to hit.
Event driven is indeed a great choice most of time. Still, Monolith can make sense sometimes, ex. if you're an early stage startup building your MVP. The overhead of building a full blown distributed system can work against your short term business goals of keeping the company alive. Most successful startups started this way including amazon. It's a balance to find between biais for action and insist on higher standards.
Agreed. That said, you can decouple parts of the system in a monolith in a way that allows you to evolve to event driven down the track. Really the root of it is to have well defined APIs through the different chunks of a system, because then how part a talks to part b can change without changing the language itself.
Agreed that Monolith still has its use cases. However, people sometimes fall into the trap they design a system that would be a monolith in the early days only because it's assumed to be faster to develop. However, they still want it to be event-driven in the long term, so a lot of effort was spent to prepare for this future, which often comes much sooner than expected. I think a crucial difference nowadays is building an event-driven system can be much much more straightforward than before by adopting various tools/services, including but not limited to AWS. If teams had those tools/services available in the old days, they probably would have started a different way.
@@Ivan-zm8kv 100% - Early stage CTO is required to make the most of team strengths, product requirements and time to market while keeping technical debt controllable.
I'm hooked on every word. I recently read a similar book, and I'm completely hooked on every word. "Mastering AWS: A Software Engineers Guide" by Nathan Vale
I can't believe Event Driven architecture is somehow the theme of this event because I have been seeking out videos on exactly this topic the last few days! Event Driven Microservices Architecture in the Cloud to be exact. Which has lead me to talks from GOTO; InfoQ, Devoxx and the like. But the more I look into the topic, the more of a macro view I have been seeking inorder to gain clarification on the pros and cons and other possible options to event Driven.... It's just really crazy coincidental that this happens to be the same topic of this keynote! Especially since I felt I was really behind when looking into this topic, in surprised to see it the subject of this latest talk! Not only is it kind of old but I feel there isn't an exact model of event driving that everyone agrees on... Except maybe Kafka implementation? But still... Event Driven architecture with little encapsulated entities wrapped with specific commands by an overall orchestrator and sent traveling down the event stream... Anyways, this is crazy... I just wish it was a GCP talk instead of AWS because that's the Cloud I'm investing in!
Hey Graham, if you're looking for more content on EDA and event-driven microservices, check out our channel -- lots of content from the last 2 years of EDA Summit events with guests from AWS, GCP, Solace, SAP, Boomi, Red Hat, etc. as well as many companies who have successfully implemented EDA talking about benefits and challenges. ua-cam.com/users/EDASummit
I don't think the metaphor in the beginning of the video is good. Our application can do multiple jobs concurrently with synchronous rpc calls if we use multiple "threads". And we can just use batch API, which is synchronous, for handling multiple orders or french fries.
In my mind the metaphor is not meant apply to that depth. Here is another way of looking at it; Let's say you application is what runs the restaurant, if the restaurant expanded to two or three more, can you evolve the application or not.
His focus was on composability, not minimizing operator count, and starting with a (dumb) cat whose output is then grepped is conceptually more elegant
For next re:Invent, we need air coolers installed on the stage just to make Dr's life easier. Those lights emit a lot of heat.
He could also take care about his fitness :)
He is just a sweaty fatty.
Or he generated the heat himself, by burning a massive amount of energy to move that round body around.
@@duongdeptraiqua If walking around at 1km per hour generates this amount of sweat, I think it's safe to say there's something not 100% right :-D It was a great great talk though.
8 hours flight listening to Werner Vogels changed my way of thinking and doing things. thanks
Loved the way they displayed the drawbacks of synchronous communication, when she was frying the fries one at a time, that was epic!
when her taking the order better showcased missing asynchronicity while the frying was just lack of parallel threads .... thinking about it, both do not hit the aynchronous feature of asynchronicity I would describe as "stop waiting" or "just react".
More than anything AWS specific, I enjoyed Dr. Werner Vogel's thought process and big-picture thinking. As a former ecologist, I was delighted by his connections of the natural world to concepts such as asynchrony, loosely coupled vs tightly coupled systems, and that individuals must evolve or die. The fact that his ideas outshown any AWS specifics when I'm a AWS fan and happily use it at work, is perhaps a testiment to him being a great thinker and presenter.
My enterprise architect REALLY needs to see the first hour of this talk
Lots of achitects and developers do… lol
That's an interesting thing. What Werner is talking about requires alignment across EA, Solution and Software Architect roles (or depending on the size of your company, that might be CTO/Architecture/tech lead, or Head of tech/Senior Engineers and Junior Engineers). It also depends on whether you are green fields or legacy as well. There are often many more things to resolve. Just doing a straight pivot to a new way of working may be beyond the financial capacity of your business to realise, or not align with the targets the product team need to hit.
This talk cleared my mind about the architecture of a SaaS idea. The Werner passion's is contagious. Great job!!!!
The annual stress of hoping Werner gets through his keynote without going into cardiac arrest
😄
😂 watching him struggle through that was stressful.
I thought maybe I was the only one thinking that. He has a great mind. I hope he takes care of himself so it keeps going!
yep, that's what I was thinking too lol it makes it hard to watch
Who has to mop the stage after him?
i love how he connects these evolved, complex and robust systems back to the basic building blocks -- events, pipes, interrupts, etc
This topic is exactly what I was looking for for the past 1 week
Exciting as always - Dr. Vogels!!
Werner's keynotes are the best!
Event driven is indeed a great choice most of time. Still, Monolith can make sense sometimes, ex. if you're an early stage startup building your MVP. The overhead of building a full blown distributed system can work against your short term business goals of keeping the company alive. Most successful startups started this way including amazon. It's a balance to find between biais for action and insist on higher standards.
Agreed. That said, you can decouple parts of the system in a monolith in a way that allows you to evolve to event driven down the track. Really the root of it is to have well defined APIs through the different chunks of a system, because then how part a talks to part b can change without changing the language itself.
Agreed that Monolith still has its use cases. However, people sometimes fall into the trap they design a system that would be a monolith in the early days only because it's assumed to be faster to develop. However, they still want it to be event-driven in the long term, so a lot of effort was spent to prepare for this future, which often comes much sooner than expected. I think a crucial difference nowadays is building an event-driven system can be much much more straightforward than before by adopting various tools/services, including but not limited to AWS. If teams had those tools/services available in the old days, they probably would have started a different way.
@@morosis82 100% !!!!! I believe this is the right approach in this case.
@@Ivan-zm8kv 100% - Early stage CTO is required to make the most of team strengths, product requirements and time to market while keeping technical debt controllable.
I argue that event driven is pretty easy to build from the get-go nowadays, so the biggest tradeoff is becoming more irrelevant
Werner never finishes a talk without talking about dynamodb
If you personally created something so impactful in cloud computing, wouldn't you want to talk about it all the time?
love the valve/ Half Life / Lambda cross over shirt.
Serious Black Mesa Research vibes
I'm hooked on every word. I recently read a similar book, and I'm completely hooked on every word. "Mastering AWS: A Software Engineers Guide" by Nathan Vale
Love this talk, and the production. Every developer/architect should watch this.
😀 🙌
Outstanding intro!
Amazing talk on many different topics
Warner rocks!
I can't believe Event Driven architecture is somehow the theme of this event because I have been seeking out videos on exactly this topic the last few days! Event Driven Microservices Architecture in the Cloud to be exact. Which has lead me to talks from GOTO; InfoQ, Devoxx and the like. But the more I look into the topic, the more of a macro view I have been seeking inorder to gain clarification on the pros and cons and other possible options to event Driven.... It's just really crazy coincidental that this happens to be the same topic of this keynote! Especially since I felt I was really behind when looking into this topic, in surprised to see it the subject of this latest talk! Not only is it kind of old but I feel there isn't an exact model of event driving that everyone agrees on... Except maybe Kafka implementation? But still... Event Driven architecture with little encapsulated entities wrapped with specific commands by an overall orchestrator and sent traveling down the event stream...
Anyways, this is crazy... I just wish it was a GCP talk instead of AWS because that's the Cloud I'm investing in!
Go AWS
By the way has a lot of great presentations to watch out about this theme
Hey Graham, if you're looking for more content on EDA and event-driven microservices, check out our channel -- lots of content from the last 2 years of EDA Summit events with guests from AWS, GCP, Solace, SAP, Boomi, Red Hat, etc. as well as many companies who have successfully implemented EDA talking about benefits and challenges. ua-cam.com/users/EDASummit
why GCP?
You should look into Solace if you want your applications to be able to connect in any hybrid cloud set up or with customer and partners.
Intro goes hard 🔥🔥🔥
Werner in Matrix is priceless. I will never see French fries the same 😂😂😂
What a production! It was really good thank you Vogels
Thanks for your feedback, Berrin! ❤️ Great to hear that you enjoyed the production. 🙌 ☁️
1:48:14
Warning Werner⚠: that 1st number is supposed to be #Septemvigintillion.😅
The world is really asychronous. Keep it up AWS.
Werner is the best! Love the show he creates and the passion!
Awesome keynote. Just about the solution for climate change and all that....
Amazing intro and very interesting topic
Do they even record the live violin music played before this. it was so good. lf any one has a link for that, please do share...
Great talk!!!! thank you
best talk ever!
The ocean, not trees are the best carbon capture mechanism btw - also Co2 is not a problem, and used to be much higher as seen in a.o. Greenland ...
Excellent 👍
I would love the see how TrustPilot monitors that system.
What is the technology behind the event broker? Do they use Solace?
Where is the source code for the readme service example?
Oh, deers! Now, I dont feel so bad about the King Viserys' hunting scene )
Go Build!
진짜 개쩌는 인트로다 ㄷㄷ...
Great talk. Amazon, please make this guy go see a cardiologist
Someone please give this man a towel next time!
Do we really need quantum computing to know that decomposing organic material makes a good fertilizer?
1:04:25 “keyboard, screen, mouse, finger”
AWS should provide vulnerability check security services for free. For small business it is not sustainable to provide security with a cost.
that's cool, only God can make a world work synchronously without failure
Video should be titled : How to get a huge AWS bill lol
I like his shirt.
Who turned off the A/C? 😅
I don't think the metaphor in the beginning of the video is good. Our application can do multiple jobs concurrently with synchronous rpc calls if we use multiple "threads". And we can just use batch API, which is synchronous, for handling multiple orders or french fries.
In my mind the metaphor is not meant apply to that depth. Here is another way of looking at it; Let's say you application is what runs the restaurant, if the restaurant expanded to two or three more, can you evolve the application
or not.
top
I was hoping for a red pill/blue pill joke about PCIe unordered IO, or Arm RC vs x86 TSO
😎😎😎😎😎😎😎😎
youtube chapters please
just like MQseries...takes me back
📱
Unnecessary use of cat by Dr. Vogels?
His focus was on composability, not minimizing operator count, and starting with a (dumb) cat whose output is then grepped is conceptually more elegant
Good talk but, with all due respect it is hard to understand his speech.
true, and the closed captions are often wrong :(
agree. but when i visited back a few days later, there is substitle with much more accuracy :)
Loosely coupled does not fit all applications. Gravity is synchronous
interesting, can you explain? Any sources or something?
No mention about massive layoffs?
When you can’t do - teach
ok Sheldon
I heard he had COVID from a collegue that was there. Would explain the amount of sweat from his head :O
The profuse sweat was distracting. He looks like he might die on stage at any moment. He should take better care of himself.
if you care that much, write him a letter and suggest some options. prick....
35:08 Useless Use Of Cat : grep "/gateway/allapi" access.log | ....