Great talk! It would be helpful to discuss how to handle teams honoring their API contracts since microservices depend so much on the proper communication and documentation of their APIs in order for this to work.
I think this was a good talk. You touched on a lot of areas that are paramount when you start thinking about a microservices architecture. I think you could definitely improve the talk by giving some more concrete examples of things like "how do you orient microservices around business capabilities" and possibly on the difference of thinking between developing in a monolith and in a distributed services architecture. You touched on it when you were talking about pitfalls of distributed transactions and cascading errors but I think you could make it a little more clear. That's an abstract concept that is essential for being successful in this type of architecture.
Some general feedback: the tweet slides were nearly impossible to read from further back in the room. I really liked how you set up the whole purpose of your talk by working through the background of why monolithic applications can be problematic with sufficiently complex or longer-lived projects and how microservices can solve that. Keep it up!
Comments
Comments are closed.
Awesome!
Great talk! It would be helpful to discuss how to handle teams honoring their API contracts since microservices depend so much on the proper communication and documentation of their APIs in order for this to work.
I think this was a good talk. You touched on a lot of areas that are paramount when you start thinking about a microservices architecture. I think you could definitely improve the talk by giving some more concrete examples of things like "how do you orient microservices around business capabilities" and possibly on the difference of thinking between developing in a monolith and in a distributed services architecture. You touched on it when you were talking about pitfalls of distributed transactions and cascading errors but I think you could make it a little more clear. That's an abstract concept that is essential for being successful in this type of architecture.
Some general feedback: the tweet slides were nearly impossible to read from further back in the room. I really liked how you set up the whole purpose of your talk by working through the background of why monolithic applications can be problematic with sufficiently complex or longer-lived projects and how microservices can solve that. Keep it up!
My feedback basically echoes Jeff's sentiments. Definitely tweak and continue submitting this talk! :)
Great talk, it covered the topic well and was well organized.
Speaker was funny and very informative.
Slides were a little simiplistic but the talk made up for it.
@Jeff Carouth: Thanks for pointing out that the tweets were not readable. Will see how to cope with the situation.
Great session all around. One of the highlights of the event for me.