Pretty sure the Spine Model is a variation on the Toyota Production System spine - see chapt 10 of 'This is Lean' by Niklas Modig and Par Ahlstrom. Great model, use it all the time to help clients understand why IT-first & org second approaches often fail.
Around 10:00 I think you said that wrong. Your two examples were “Q: should I use docker? A: 1000 Yes” “Q:Should I NOT use docker? A: 1000 No”. That basically means you got 2000 yes answers. I assumed you were trying to say it’s 50/50 but can look skewed depending on what you search.
Very valuable resources and insights! Though he mentions the word microservice in every other sentence, which negates his wise words on cargo cult a bit.
Thanks Machiel! I know where you are coming from here, but it's difficult not to mention something when you are talking about it as a concept :-) I'm definitely keen to stress that "microservices" is fundamentally about good architecture!
Thanks for the troll Anti - very constructive :-( The comparison is not like-for-like, rather I was making the point that it is very easy to couple your architecture to both an ESB or API Gateway
Nice talk, Daniel. I ran an ESB team for several years and Daniel's point is spot on. Since the ESB team has to deal with all the transformation logic needed to integrate the various systems, you end up building a big black box of logic that only the ESB team understands. The same pattern can play out with an API Gateway if you're not careful. Let it do what it's good at (authentication, monitoring, etc.), but push the other responsibilities to the back-end services and make them deal with them.
Very important topic and very good speach about! Thanks you, Daniel.
Pretty sure the Spine Model is a variation on the Toyota Production System spine - see chapt 10 of 'This is Lean' by Niklas Modig and Par Ahlstrom. Great model, use it all the time to help clients understand why IT-first & org second approaches often fail.
The GO mascot is so hard to look at.
Great stuff. Thank you! :)
I wish there waa a summary of the main points because as a novice in the area, i dont have experience i can correlate to his points.
Around 10:00 I think you said that wrong. Your two examples were “Q: should I use docker? A: 1000 Yes” “Q:Should I NOT use docker? A: 1000 No”. That basically means you got 2000 yes answers. I assumed you were trying to say it’s 50/50 but can look skewed depending on what you search.
i didn't get anything, but was very interesting!
Listening to Daniel's talk, sounds like I'm hearing myself talk :D (loved this session, naturally)
Very valuable resources and insights! Though he mentions the word microservice in every other sentence, which negates his wise words on cargo cult a bit.
Thanks Machiel! I know where you are coming from here, but it's difficult not to mention something when you are talking about it as a concept :-) I'm definitely keen to stress that "microservices" is fundamentally about good architecture!
Yeah!
How to move from dev to architect
In enjoyed the talk very much, thankyou, but you really speak too fast :)
Comparing ESB to an API Gateway is like comparing Tomatoes with Apples. I guess you never worked with an ESB.
Thanks for the troll Anti - very constructive :-( The comparison is not like-for-like, rather I was making the point that it is very easy to couple your architecture to both an ESB or API Gateway
Nice talk, Daniel.
I ran an ESB team for several years and Daniel's point is spot on. Since the ESB team has to deal with all the transformation logic needed to integrate the various systems, you end up building a big black box of logic that only the ESB team understands. The same pattern can play out with an API Gateway if you're not careful. Let it do what it's good at (authentication, monitoring, etc.), but push the other responsibilities to the back-end services and make them deal with them.
Language dependent *LOL*