Mark Richards

Enterprise Architecture Fundamentals

Monday, 9:00 AM EST

A 2007 Gartner survey found that 40% of all enterprise architecture efforts were failing or had failed. One of the primary reasons for these failed attempts at enterprise architecture is that no one really knows what it is or how to properly establish and run an effective enterprise architecture program. Interestingly enough, a 2015 Gartner survey showed that 70% of all businesses were looking to start or restart their enterprise architecture programs. That’s where this workshop comes in.

Enterprise architecture is more than drawing lots of enterprise-level future-state architecture diagrams – it is about being able to bridge the gap between business needs and IT capabilities, integrate systems across the enterprise, consolidate information from various systems, and knowing when and how to use enterprise architecture models. In this workshop you'll learn what enterprise architecture is, the modern role of an enterprise architect, and the steps involved in creating en effective enterprise architecture.

Introduction

• Enterprise architecture context
• Enterprise architecture goals
• Do you need enterprise architecture?
• Enterprise architecture roadmap
  
  

Enterprise Architecture Frameworks & Tools

• Framework purpose and goals
• Zachman
• TOGAF
• TAFIM
  
  

Enterprise Architecture Models

• IT capabilities models
• Information models
• Prioritization models
• Initiative models
• Enterprise model synergy
  
  

Enterprise Architecture Strategies

• Prescriptive strategy
• Classic alternatives strategy
• Distributed strategy
• Durable interface strategy
  
  

Transforming the Enterprise

• Architectural roadmaps
• Organizational roadmaps
• Technical roadmaps
• Business automation roadmaps
• Roadmap synergy
• Roadmap vitality assessment
  
  

Creating a Modern EA Practice

• Introducing agility to your EA practice
• Evolving the enterprise
• Breaking down barriers
• What doesn’t work
• Skills required for an enterprise architect
• EA as a business or technical function
  
  

Summary and Wrap-up

• Next steps
• Architecture resources

Architectural Modularity

Tuesday, 8:30 AM EST

It seems like all we talk about these days is making our architectures more modular. Buy why? In this session I will discuss the drivers and reasons why it is essential to move towards a level of modularity in our architectures. I will discuss and show real-world use cases of distributed modular architectures (specifically microservices and service-based architecture), and then discuss in detail the core differences between microservices and service-based architecture and when you should consider each. I'll end the talk by discussing the most effective way of migrating to modular distributed architectures.

Agenda:

• Drivers for modularity
• Modular distributed architectures
• Microservices vs. service-based architecture
• The move towards modularity

Microservices AntiPatterns

Tuesday, 10:30 AM EST

Even though teams are gaining more experience in designing and developing microservices, nevertheless there is still a lot to learn about this highly distributed and somewhat complicated architecture style. Unfortunately, lots of microservices anti-patterns and pitfalls emerge during this learning curve. Learning about these anti-patterns and pitfalls early on can help you avoid costly mistakes during your development process. While anti-patterns are things that seem like a good idea at the time and turn out bad (see martinfowler.com/bliki/AntiPattern.html), pitfalls are those practices that are never a good idea at the time - ever. In this session I will cover some of the more common anti-patterns you will likely encounter while creating microservices, and most importantly describe some of the techniques for avoiding these anti-patterns.

Agenda

• Function-Driven Identification AntiPattern
• I Was Taught to Share AntiPattern
• The Timeout AntiPattern
• Hop on the Bus AntiPattern
• Data-Driven Migration AntiPattern

Microservices Pitfalls

Tuesday, 1:30 PM EST

Even though teams are gaining more experience in designing and developing microservices, nevertheless there is still a lot to learn about this highly distributed and somewhat complicated architecture style. Unfortunately, lots of microservices anti-patterns and pitfalls emerge during this learning curve. Learning about these anti-patterns and pitfalls early on can help you avoid costly mistakes during your development process. While anti-patterns are things that seem like a good idea at the time and turn out bad (see martinfowler.com/bliki/AntiPattern.html), pitfalls are those practices that are never a good idea at the time - ever. In this session I will cover some of the more common pitfalls you will likely encounter while creating microservices, and most importantly describe some of the techniques for avoiding these pitfalls.

Agenda

• Grains of Sand Pitfall
• Where's the Acid Pitfall
• Logging Can Wait Pitfall
• Jump on the Bandwagon Pitfall
• Give it a Rest Pitfall

Reactive Architecture Patterns 1

Tuesday, 3:15 PM EST

Reactive architecture patterns allow you to build self-monitoring and self-healing systems that can react to both internal and external conditions without human intervention. How would you like to design systems that can automatically grow as the business grows, automatically handle varying load (cyber Monday?), and automatically handle (and repair) internal and external errors, all without human interaction? I'll show you how to do this with your current technology stack (no special languages, tools, frameworks, or products). In this two-part session I will leverage both slides and live coding using Java and RabbitMQ to describe and demonstrate how to build reactive systems. Get ready for the future of software architecture - that you can start implementing on Monday.

Part 1 Agenda:

• Reactive systems introduction
• Channel Monitor Pattern (self-awareness)
• Consumer Supervisor Pattern (scalability and elasticity)
• Workflow Event Pattern (error handling)

Reactive Architecture Patterns 2

Tuesday, 5:00 PM EST

Reactive architecture patterns allow you to build self-monitoring and self-healing systems that can react to both internal and external conditions without human intervention. How would you like to design systems that can automatically grow as the business grows, automatically handle varying load (cyber Monday?), and automatically handle (and repair) internal and external errors, all without human interaction? I'll show you how to do this with your current technology stack (no special languages, tools, frameworks, or products). In this two-part session I will leverage both slides and live coding using Java and RabbitMQ to describe and demonstrate how to build reactive systems. Get ready for the future of software architecture - that you can start implementing on Monday.

Part 2 Agenda

• Thread Delegate Pattern (scalability)
• Threshold Adjust Pattern (automatic configuration and self-learning)
• Producer Control Flow Pattern (self-healing)

The Art of Problem Solving

Tuesday, 8:30 PM EST

As Tech Leaders, we are presented with problems and work to find a way to solve them, usually through technology. In my opinion this is what makes this industry so much fun. Let's face it - we all love challenges. Sometimes, however, the problems we have to solve are hard - really hard. So how do you go about solving really hard problems? That's what this session is about - Heuristics, the art of problem solving. In this session you will learn how to approach problems and also learn techniques for solving them effectively. So put on your thinking cap and get ready to solve some easy, fun, and hard problems.

Agenda:

• the checklist
• visual representations
• you know what happens when you assume…
• you gotta start somewhere
• the world is flat
• hey! keep it clean!
• perception can be reality

Integration Architecture: Concepts and Patterns

Wednesday, 9:00 AM EST

Very few applications stand alone anymore. Rather, they are combined together to form holistic systems that perform complex business functions. One of the big challenges when integrating applications is choosing the right integration styles and usage patterns. In this session we will explore various techniques and patterns for application integration, and look at what purpose and role open source integration hubs such as Camel and Mule play in the overall integration architecture space (and how to properly use them!). Through actual integration scenarios and coding examples using Apache Camel you will learn which integration styles and patterns to use for your system and how open source integration hubs play an part in your overall integration strategy

Agenda:

• Integration Styles: pros, cons, and when to use
• Integration and Abstraction
• Integration Hubs: use cases, failover, federation, team ownership
• Common integration patterns

Enterprise Architecture Fundamentals

Wednesday, 11:00 AM EST

Too many companies embark on enterprise architecture efforts only to have them fail. One of the biggest reasons for these failed attempts at enterprise architecture is that no one really knows what it is. Ask 10 people what enterprise architecture is, and you are guaranteed to get 10 different answers. Enterprise architecture is more than drawing lots of enterprise-level future-state architecture diagrams – it is about being able to bridge the gap between business needs and IT capabilities. In this session you will learn about the context and goals of enterprise architecture, what skills are necessary to become an enterprise architect, and how to model the enterprise. We'll also take a look at transformation techniques for both data and systems across the enterprise.

Agenda:

• What is enterprise architecture?
• Enterprise architecture goals
• Enterprise architecture frameworks
• Enterprise architecture core models
• Enterprise architecture initiatives
• Enterprise architecture transformation techniques
• Enterprise architecture communication strategies
• Enterprise architecture roadmaps
• Enterprise architecture resources

The Soft Skills of Architecture Part 1

Wednesday, 1:30 PM EST

Being a software architect is a tough job. Not only do you have to have significant technical depth and breadth, but you also need to understand the business domain you are working in. While these aspects are important, there is another perhaps more vital aspect of being an architect - the soft skills. Too many architects fail to realize the importance of soft skills, and as a result do not achieve success in their career as an architect. In this two-part session I will focus on the soft skills of architecture. In part one I will cover skills related to techniques such as architecture decisions, architecture refactoring, and communicating your software architecture through diagrams, documentation, and presentation.

Agenda:

• Architecture decisions
• Architecture refactoring techniques
• Communicating your architecture

The Soft Skills of Architecture Part 2

Wednesday, 3:15 PM EST

Being a software architect is a tough job. Not only do you have to have significant technical depth and breadth, but you also need to understand the business domain you are working in. While these aspects are important, there is another perhaps more vital aspect of being an architect - the soft skills. Too many architects fail to realize the importance of soft skills, and as a result do not achieve success in their career as an architect. In this two-part session I will focus on the soft skills of architecture. In part two I will cover the people skills side of architecture, including working in architecture teams, making implementation teams effective, negotiation techniques, and leadership skills.

Agenda:

• Working in architecture teams
• Making implementation teams effective
• Negotiation skills
• Leadership skills