The Integration Architect's Toolkit
The Integration Architect's Toolkit
About the Bundle
This bundle combines two great books at an unbeatable price that every integration architect should have. Inspired by Enterprise Integration Patterns book, Camel Design Patterns focuses on application integration with Apache Camel. 37 Things adds the wisdom of years one architect should know about. Taken together, they teach architecture principles in breadth and integration at depth.
Gregor and Bilgin believe you'll enjoy both books, and want to offer them together at a discounted price.
Camel Design Patterns
Patterns, Principles, and Practices for Designing Apache Camel Applications
Hardcover Book is available on Lulu: http://www.lulu.com/spotlight/camel_design_patterns
The e-book is also available on Amazon: http://www.amazon.com/dp/B01D1RERQG
There are great books about Apache Camel already, but this book is a little bit different. Here is why. Throughout the building of a Camel application, there are many levels of design decisions to be made. Knowing the Camel framework and the Enterprise Integration Patterns (EIPs) is a must, but not enough to design a real-world integration application. Mastering such applications requires an understanding of EIPs, messaging, Microservices, and SOA principles, and distributed system concepts as a whole.
Driven by real-world experiences, this book consolidates the most commonly used patterns and principles for designing Camel applications. For each pattern, there is a problem description with a context, a proposed solution, and Camel specifics, plus tips around the implementation. Patterns range from individual Camel route designs for happy path scenarios, to error handling and prevention practices, to principles used in the deployment of multiple routes and applications for scalability and high availability purposes.
The patterns listed here are not new; they are all over the Internet, described many times under various categories and names. Here they are described from a practical point of view with an emphasis on implementing these patterns in Apache Camel, rather than academical pattern definition. And lastly, this book is not a step-by-step guide for writing Camel routes. Instead, it is a series of high-level use cases demonstrating different patterns used for creating modern Camel applications. No code, just pragmatic theory.
I believe you will find this short and focused book useful.
37 Things One Architect Knows About IT Transformation
A Chief Architect's Journey
This book helps architects, CTOs, and CIOs drive large-scale enterprise IT transformation.
Many large enterprises are feeling pressure from the rapid digitalization of the world: digital disruptors attack unexpectedly with brand-new business models; the "FaceBook generation" has dramatically different user expectations; and a whole slew of new technologies has become available to everyone with a credit card. This is tough stuff for enterprises that have been, and still are, very successful, but are built around traditional technology and organizational structures. "Turning the tanker", as the need to transform is often described, has become a board room-level topic in many traditional enterprises. Not as easily done as said.
Chief IT Architects and CTOs play a key role in such a digital transformation endeavor. They combine the technical, communication, and organizational skill to understand how a tech stack refresh can actually benefit the business, what "being agile" and "DevOps" really mean, and what technology infrastructure is needed to assure quality while moving faster. Their job is not an easy one, though: they must maneuver in an organization where IT is often still seen as a cost center, where operations means "run" as opposed to "change", and where middle-aged middle-management has become cozy neither understanding the business strategy nor the underlying technology. It's no surprise then that IT architects have become some of the most sought-after IT professionals around the globe.
This book supports IT architects with the skills necessary to become effective not just in systems architecture, but also in shaping and driving the necessary transformation of large-scale IT departments. In today’s world, technical transformation and organizational transformation have become inseparable.
Organized into 37 episodes, this book explains:
- The role and qualities of an architect in a large enterprise
- Architecture at enterprise scale
- Communicating to a variety of stakeholders
- Understanding organizational structures and systems
- Transforming traditional organizations
Armed with these insights, architects and CTOs will be able to ride the Architect Elevator up and down the organization to instill lasting change.
Praise for 37 Things One Architect Knows:
"As a Business executive and former CTO, this is an enjoyably readable description of an IT Chief Architect’s role and practical methods of influence. I recommend this book to technical staff aspiring to become Chief Architect or CTO." -- Matthew Rawlings, Head of Middle Office and Operations, Bloomberg LP
"Great architects have battle scars and stories to tell. 37 Things reveals a journey that gives character to Gregor’s battle scars and demonstrates how to achieve architecture awesomeness." -- Alexandre Lopes Global Head of Architecture and Service Design, Zurich Insurance Company Ltd
"Gregor shares his hard-learned lessons about enterprise IT using a witty pen. 37 Things has the potential to become a classic for those who need to understand the forces surrounding the IT function in large enterprises. It deserves to be read by an audience far larger than those working on the inside of IT." -- Einar Landre, Leading Analyst IT, COO CIT DIG, Statoil ASA
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms