Keynote in English - US at DomCode 2016
Short URL: https://joind.in/talk/8c4a6
(QR-Code (opens in new window))
Here Be Dragons! What It's Really Like to Slay a Monolith
Comments
Comments are closed.
A great talk about the advantages of, and the obstacles, of making larger scale architectural changes to an organisation moving towards the use of microservices.
Good talk, but a bad fit for the conference format.
Need to talk slower and clearer though (mostly due to venue bad acoustics)
Interesting talk but I would have liked more in depth stuff.
Very good talk. Learned a lot from it. Could've adapted the speed of speaking to the venue. The acoustics of this venue really don't allow for fast speaking. It was a trap many speakers in the main hall fell into. Aside from that, I really loved this talk.
Good overview talk, which was fine for a keynote of course, but I'd like a bit more in depth stuff, just my personal preference though. I do think it could've be emphasised that microservices isn't actually a silver bullet, and a monolithic application can actually be better.
Great talk! For me it was the ideal path as most speakers are telling us. Where I'm interested in; how long such a process will take? How many problems there are on the road passed in review. Maybe it's possible to add some details of the transitioning from a legacy monolithic application towards a group of services? Despite this a good talk!
Great to hear a 'war story' on slaying the monolith and 'selling' the micro service vision inside your company. I had the impression that Graham tried to compensate for the time lost on replacing the beamer (not his fault in any way), the speed of talking made it a little hard to comprehend.
Good stuff here. Am in the middle of the process of slaying a monolith and got some good insights here.
I really liked this talk, because even if you take away the monolith to microservices backstory, you still have some very solid advice on how to get acceptance for a big change within an organisation and within a development team.
due to the fact that there were programmers from multiple languages it could have been a bit less PHP minded. Instead of showing the packages used a sentence like: `don't re-invent the wheel: use existing packages` would have been enough
At times, it went quite fast for a lot of information. Easy down a bit to make it easier to follow.
* great how you worked around Murphy's :)
Good talk, acoustics were bad, and a bit of adaptation for that would make this a great performance.