Since introducing the
first architecture blueprint focused on omnichannel integration, we've been looking at how to integrate with
Software as a Service (SaaS) applications.
It's an interesting challenge in that we've been given the mission of creating architectural content based on common customer adoption patterns. That's very different from most of the traditional marketing activities usually associated with generating content for the sole purpose of positioning products for solutions. When you're basing the content on actual execution in solution delivery, you're cutting out the
chaff. What's that mean?
It means that it's going to provide you with a way to implement a solution using open source technologies by focusing on the integrations, structures, and interactions that actually have been proven to work. What's not included are any vendor promises that you'll find in normal marketing content. Those promised that when it gets down to implementation crunch time, might not fully deliver on their promises.
Enter the term Architectural Blueprint.