Working Draft This site is currently a working draft of the ITABoK 3.0. Release date is planned for beginning of 2018. In the meantime please utilize the current ITABoK version 2.0 Definition Value Streams represent how and organisation configures it's business capabilities to deliver value to an internal or external stakeholder typically a
This blog post is one in a series that will give you some insight into the full day training class (Microservices Solution Architectures) I will be teaching at the ITARC Austin on October 6th, 2016. That's a great question. Maybe you shouldn't. I have had this debate with more than one person: "Isn't a microservices architecture just
by Sanjeev Azad If you haven’t heard of BLOCKCHAIN so far then I am sure it’ll be coming to your way soon. As there are lot of challenges into the current enterprise systems especially financial institutions where people are losing trust due to centralized control over data and little transparency, this topic will brief how
by Ganesh Prasad With over a decade’s worth of SOA experience at varied organisations, Ganesh has discovered the secret to unlocking SOA’s wasted potential. He aims to reignite SOA practice with a fresh, lightweight yet rigorous method based on the single most important element that underlies all types of system interactions – the notion of dependencies.
Paul Preiss: SOA contrast, just a contrast. Your physical reaction, I think, was a good start. I'm just asking for your basic contrast for the- if we're in a conference and I'm another architect, I don't understand the difference between Microservices and SOA. Venky: The SOA, it gives a more structural layered approach to doing
In my part of the world, it's not uncommon for people to say that someone wouldn't recognize something if it "bit them in the [rude rump reference]". For many organizations, that seems to be the explanation for the state of their enterprise IT architecture. For while we might claim to understand terms like "design", "encapsulation",
Technical Empathy - the ability to see the system from the point of view of the caller of your code, not just the point of view of your code— Michael Feathers (@mfeathers) January 26, 2015 Michael Feathers' tweet about technical empathy packs a lot of wisdom into 140 characters. Lack of technical empathy can lead
By Mark Sigda I have to admit, as an architect with a long history in distributed systems, that I still love the concept of SOA. I’ve also tried to make it happen (more than once) and failed miserably. As a former developer, something always troubled me about SOA. I didn’t see it at the