CNCF fail. Pro tip: even if a talk goes overtime, and it seems like this one didn’t, the impact on a conference schedule last for a day. On youtube the talk will be incomplete forever.
this talk deserved an encore, a long Q&A and another encore. to be cut off is ridiculous. impacting a conference for 2 minutes is nothing compared to a cliffhanger that's 3 years later and 74,000 views old and counting
One of the best talks i have listened to on Go. The middleware reminds of NodeJS/expressJS patterns. Concepts, problems and potential solutions are explained very well.
5th April 2023 14:37 IST : I had an idea that Go Lang was the mostly used language for good number of CNCF Projects and Peter told that those are rather Micro-Services oriented . So I knew that out of those valuable frameworks offered by Go there has to some specific framework which would rather be suited the best for these projects . M Glad I came across this video . Thanx CNCF and Peter !
Listened to the whole thing. Seems very relevant to the industry on how we see things in a day. Im transitioning to Go as well. Didnt want the talk to end this quickly.
I am not complaining about the last 2 minutes. Great talk Peter, very helpful. I like your diction! Talk about teaching us a new language; I suppose that is the nature of our endeavors, to sprinkle effective instruments of thought(in this case words) in an optimal(articulate) fashion.
This is exactly what iv been thinking about for a while, to create a foundation for a microservice that is identical on all distributed services and can be bootstrapped easily for new services without making too many changes. The distributed service should be like a cell, each cell has organelles that perform basic functions, creating energy, signalling other cells, creating proteins etc... This structure is the same for each cell, yet each cell also has very specific functions, like the skin cell, the brain cell, the liver cell etc... When you put cells together you get an "ecosystem" that works together in harmony to produce larger functions of the "body", combined with a container orchestration layer you can now have cells failing and yet the system can maintain balance by routing requests to healthy cells which pick up the slack. You have an event driven infrastructure in place for cells to signal what is happening in the system to other cells that are interested, you can plugin to this stream of information (Kafka) as a person standing outside of the system and monitor the health of the system through the messages being sent. This makes it possible to diagnose the system through various markers and debug "metabolic pathways" that are showing a lot of failure so to speak. I'm in the process of creating such a "cell" template as a hobby in GO, the idea is to implement a "perfect" service shell which can be bootstrapped easily and be ready for immediate business implementation at its core without fussing about the peripheral behavior.
Bruh that cell analogy just fucked something on my mind. Very interesting analogy. Designers get inspirations from nature, is it perhaps our time to do the same?
Go is magic due it's way to tell if an structure is implementing an interface or not, it magically connects you to it if you implement the methods, but it's not explicitly told
A very insightful talk and something I am currently trying to draw inspiration from, for my own service blueprint: github.com/preslavrachev/go-service-template I am about to incorporate rate the concept of middlewares in there too. Too bad, they cut off the talk a couple of minutes too early.
I don't like it. Probably looks okay for a small example demonstrated, but going to grow in complexity pretty soon for even average sized applications. Will result in many shallow interfaces. Will be difficult to keep track of number of middlewares and the functionality they provide.
wtf ending. booooooo to whoever cut this off. cool talk btw, im sort of doing some survey on how to write microservices on other languages...go does not seem to be that mature (at least 4 years ago...)
it's a shame he spent the first 12 minutes of the presentation trying to sell go, otherwise he would've had more time to cover the rest and open for questions! I assume most of the people coming to this talk is already sold by lots of other nice "go is awesome" presentations!
Four years later and this is still one of the best talks, no doubts. I really want to know if those 2 minutes worth it? Kudos to Peter Bourgon!
7 yrs later and same!
CNCF fail. Pro tip: even if a talk goes overtime, and it seems like this one didn’t, the impact on a conference schedule last for a day. On youtube the talk will be incomplete forever.
Absolutely... What a shame really! Now we will never know what he had to say last.
this talk deserved an encore, a long Q&A and another encore. to be cut off is ridiculous. impacting a conference for 2 minutes is nothing compared to a cliffhanger that's 3 years later and 74,000 views old and counting
One of the best talks i have listened to on Go. The middleware reminds of NodeJS/expressJS patterns. Concepts, problems and potential solutions are explained very well.
Probably one of the best talks I've ever heard
until the end! what kind of nonsense was that!
It so cool to get a talk from a Final Fantasy villain
Fantastic talk!
5th April 2023 14:37 IST : I had an idea that Go Lang was the mostly used language for good number of CNCF Projects and Peter told that those are rather Micro-Services oriented . So I knew that out of those valuable frameworks offered by Go there has to some specific framework which would rather be suited the best for these projects . M Glad I came across this video . Thanx CNCF and Peter !
Listened to the whole thing. Seems very relevant to the industry on how we see things in a day. Im transitioning to Go as well. Didnt want the talk to end this quickly.
I've started using go kit to build microservices in go and it's awesome :)
Go kit part of the talk starts 18:39. Before that, it's just a very long introduction.
I am not complaining about the last 2 minutes. Great talk Peter, very helpful. I like your diction! Talk about teaching us a new language; I suppose that is the nature of our endeavors, to sprinkle effective instruments of thought(in this case words) in an optimal(articulate) fashion.
Really unfortunate that lady had to cut him off, very unprofessional.
Fantastic. Thanks Very Much!
Hilarious and timely. Would watch again.
Seriously, what kind of beaurocrat cuts a talk off 2mins before it finishes.
haha that was such a downer at the end, incredible rude!
That was very bad cutting off at the very end...
technical debt is forever.
Great points regrading this micro service paradigm.
that lady just pissed off everybody including people here!
Nice talk!
Does he have the same talk elsewhere with a complete uninterrupted end?
Thanks Karen at the end there
Brilliant talk, so unfortunate that is left unfinished....
Very helpful. Thank you, Peter!
Really interesting talk. Such a shame he got cut off at the end.
Great talk by Peter Bourgon, the woman at the end should be ashamed of herself.
This is exactly what iv been thinking about for a while, to create a foundation for a microservice that is identical on all distributed services and can be bootstrapped easily for new services without making too many changes. The distributed service should be like a cell, each cell has organelles that perform basic functions, creating energy, signalling other cells, creating proteins etc... This structure is the same for each cell, yet each cell also has very specific functions, like the skin cell, the brain cell, the liver cell etc...
When you put cells together you get an "ecosystem" that works together in harmony to produce larger functions of the "body", combined with a container orchestration layer you can now have cells failing and yet the system can maintain balance by routing requests to healthy cells which pick up the slack. You have an event driven infrastructure in place for cells to signal what is happening in the system to other cells that are interested, you can plugin to this stream of information (Kafka) as a person standing outside of the system and monitor the health of the system through the messages being sent. This makes it possible to diagnose the system through various markers and debug "metabolic pathways" that are showing a lot of failure so to speak.
I'm in the process of creating such a "cell" template as a hobby in GO, the idea is to implement a "perfect" service shell which can be bootstrapped easily and be ready for immediate business implementation at its core without fussing about the peripheral behavior.
Bruh that cell analogy just fucked something on my mind. Very interesting analogy. Designers get inspirations from nature, is it perhaps our time to do the same?
Great talk on go!
Great talk, thanks Peter, he talks fast but every word brings so much more. It was so unprofessional to cut him.
Really like Peter Bourgon, it's a shame that those 2 minutes got cancelled!
Does anyone know where this presentation is?
I'm new to this microservices niche
I wanna know the end to :-)
Explained very well it was brilliant talk
A great talk. Loved it. But the ending would give it a great finish. Boo to the lady.
Are the slides available somewhere? So at least we could see the last slides ... :( Anyway great talk!
Yes its available here
peter.bourgon.org/applied-go-kit/#1
Great talk, too bad Karen had to cut it off at the end though
This talk like Lord of The Rings trilogy without Return of The Kings
Django also provides middleware...
Pity that at 2024 go-kit seems abandoned 😞Great talk though
video starts at 11:16 , initial part of video is nothing but go preaching!
Thanks
@CNCF put that lady into a goroutine, will ya ?
dequeue her channel
Aie .. the 2 additional minutes. I'm discovering that the rest are complaining from the same :D
Go is magic due it's way to tell if an structure is implementing an interface or not, it magically connects you to it if you implement the methods, but it's not explicitly told
What a sucky thing to do to a presenter. Should be ashamed.
好帅
And they don't even upload the slides... wtf
peter.bourgon.org/applied-go-kit/#1
speakerdeck.com/peterbourgon/go-plus-microservices-equals-go-kit
shit!! really I have some problems with log, metrics and tracing in Gokit and the woman didn't complete his presentation!
Its now 2022 and we're still wondering what he was going to say, that 'two-minute' woman is such a jobsworth
It should be okay to allow few minutes... bad he couldn't complete the talk!
A very insightful talk and something I am currently trying to draw inspiration from, for my own service blueprint: github.com/preslavrachev/go-service-template I am about to incorporate rate the concept of middlewares in there too.
Too bad, they cut off the talk a couple of minutes too early.
Dude the hair gives my ocd a run for the money
End of the talk is here: ruclips.net/video/JXEjAwNWays/видео.html
I don't like it. Probably looks okay for a small example demonstrated, but going to grow in complexity pretty soon for even average sized applications. Will result in many shallow interfaces. Will be difficult to keep track of number of middlewares and the functionality they provide.
I like his hair, I am bald though .
11:20 when he starts talking about microservices - till them he explains what is go 😑
wtf ending. booooooo to whoever cut this off. cool talk btw, im sort of doing some survey on how to write microservices on other languages...go does not seem to be that mature (at least 4 years ago...)
Why the hell would they talk this guy off stage when he was getting to the conclusion of this great talk? Idiotic
cmon 2 minutes....
it's a shame he spent the first 12 minutes of the presentation trying to sell go, otherwise he would've had more time to cover the rest and open for questions!
I assume most of the people coming to this talk is already sold by lots of other nice "go is awesome" presentations!
the woman was very rude!!!
Boo hoo, lady
it's to bad the docs and examples really are lacking for go-kit. makes it kind of un-user friendly :(
Blame it on him, should cut off the introduction by.. a lot