“Architect” – It’s one of the most overly used, abused and least understood of software engineering roles. Every senior developer thinks they are one. Many aspire to become one. The rest can’t stand them. The word takes on a totally different meaning if prefixed with development, solution or enterprise. It gets even more divided when referring to architects for technologies (i.e., UI architect, Java architect, etc.). The topic is hardly covered in formal education and every new meetup/conference will give you their perspective. Well, Mike and Rajesh have their views on it, too. Attend this Tech Talk to learn more about what being an architect really means, their role in the organization, their responsibilities and the blind spots that budding architects can fall into. About the speakers Michael Walker is the Chief Architect for CA Technologies Application Performance Management product line. In this role, he leads the architecture definition across 14 scrum teams and 4 geographies. Prior to joining CA Technologies, Michael worked as an architect at Cassat Corporation where he led the virtualization effort for their platform. Michael has also held senior engineering positions at Sun Microsystems where he worked in their System Software group and contributed to their Solaris Operating System. Rajesh Raheja is vice president for architecture and technology initiatives in the Applications Delivery BU and an enterprise software veteran of 24 years. He recently came to CA after 18 years at Oracle in various leadership roles in Communications, CRM, ERP, SaaS and SOA groups. In his most recent role, he architected, designed and led DevOps engineering for an Integration Cloud iPaaS offering; the success of which saw him assume leadership of a central cloud delivery team to on-board all integration cloud services in the PaaS division. Rajesh holds a Bachelor of Engineering degree in computer engineering from University of Bombay, one US patent on enterprise app deployment strategy and SCPM, CSM and PMC-11 certifications.

1. The Role of an Architect
Mike Walker, Chief Architect, APM
Rajesh Raheja, VP Business Unit Executive, API Management
February 2016

2. 2 © 2015 CA. ALL RIGHTS RESERVED.
About Mike
Software Engineer and Architect
§ 25+ years industry experience focusing
starting with Operating Systems and
moving through the mobile to server side
Java technologies.
§ Chief Architect – defining product
architectural roadmaps; Aligning
development across 14 scrum teams.
§ Individual Contributor, Architect, Hands on
Developer.
2013-2015: CA Technologies: Chief Architect for Application
Performance Management portfolio
2009-2013: CA Technologies. AppLogic – worked at
repurposing our technology from Cassatt to add to the
AppLogicvirtualization solution.
2006-2009: Cassatt: Small startup focusing on writing the
operating system for the data center. Architect for
Virtualization Software
2001-2006: Sun Microsystems: Mobile Application
Framework on top of J2ME, Tomcat and JSP, Sun Labs
1990-2000: Sun Microsystems working on the Solaris
Operating System.

3. 3 © 2015 CA. ALL RIGHTS RESERVED.
About Rajesh
Enterprise Technologist and Product Development
§ 20+ years delivering enterprise
applications and integration platform
technologies
§ Wore many hats: engineering
management, architecture, DevOps
engineering, solution engineering, product
management, strategy
§ Still, a hands-on architect
2015: CA Technologies API Management Integration strategy
2013-2015: Fusion Middleware SOA Integration architect,
Designed/built Oracle Integration Cloud Service iPaaS, led
SaaS devOpsenablement for Fusion Middleware Integration
2008-2011: Solution engineering/SWAT team lead for pre-
built integrations across acquired software portfolio
2005-2007: Technology strategy driving SDLC methodology
for 2000+ Fusion Applications developers
1998-2005: Engineering lead for various CRM/ERP products
including Oracle Workflow, Service Delivery Platform,
Number Portability, Marketing Online
1991-1997: Consulting engagements at global Fortune 500
companies including British Telecom, Kellogg Company and
HLP South Texas Nuclear Power Plant

4. 4 © 2015 CA. ALL RIGHTS RESERVED.
Why the focus on architecture?
§ Wikipedia. Grady Booch, Inventor, UML

5. 5 © 2015 CA. ALL RIGHTS RESERVED.
What do you think of when you hear “Architect”

6. 6 © 2015 CA. ALL RIGHTS RESERVED.
Architecture requires Investment
As an system evolves its complexity increases unless
work is done to maintain or reduce it.
Software systems undergo constant change causing the
architecture of the system to degenerate over time.
Reversing system degeneration takes extra effort…
-- Lehmans Laws of Software Evolution (1974)
-- Software Metrics, 2002. Proceedings. Eighth IEEE Symposium on
Lindvall, M. Tesoriero, R., Costa, P.

7. 7 © 2015 CA. ALL RIGHTS RESERVED.
Types of Architects
§ Development (Software) Architect – Designs the Product
§ Solution Architect – Applies the Product to a Solution
§ Enterprise Architect – Applies the Solution to the Business
Needs a mix of Business, Domain and Technologyskills
https://rraheja.wordpress.com/2010/10/01/architect-vs-solution-architect/

8. 8 © 2015 CA. ALL RIGHTS RESERVED.
Fusion Pace 3D
System
Cameras: Sony HDC-F950
and HDC-1500
Lenses: Fujinon
HA16x6.3BE (6.3-
101mm) and special
design HA5x7B-W50 (7-
35mm) custom designed
Designed By: CPG
Vince Pace, Co-Chairman
James Cameron, Co-
Chairman
Patrick Campbell, CTO

9. 9 © 2015 CA. ALL RIGHTS RESERVED.
Types of Architects

10. 10 © 2015 CA. ALL RIGHTS RESERVED.
Types of Architects

11. 11 © 2015 CA. ALL RIGHTS RESERVED.
Definition of an Architect: See the Big Picture to ensure
Technical Strategy is aligned with Business Vision
From a Team Architect level:
§ Responsible for product
components
§ Technology Evaluations based on
roadmap
§ Dependencies between product
components
To a Chief Architect/VP/CTO level:
§ Owns the portfolio architecture
§ Defines Technology Stack and
Architecture Roadmap
§ Coordinates dependencies
between teams

12. 12 © 2015 CA. ALL RIGHTS RESERVED.
Where do Software Architects fit in the Organization?
Triad
Leadership
Model
WHEN HOW
WHAT
Engineering Architecture/Technology
Product Management
Vision: Worry about the technology in
the future, because when the future’s
here, you won’t have the time! Source:
Nathan Myhrvold, former CTO Microsoft
Mission: Establish Technical Vision and
Culture in the organization, and ensure
the Technology Strategy serves the
Business Strategy.

13. 13 © 2015 CA. ALL RIGHTS RESERVED.
Core Responsibilities of Software Architect
§ Define/Ensure Compliance to Non-Functional Requirements
§ Create Architecture Definition and Technology Roadmaps
§ Perform Technology Evaluation and Architecture Reviews
§ Know about the Competition and sponsor Incubator Projects
§ See the Big Picture to ensure the architecture meets the goals!
Be a trusted advisor to the business!

14. 14 © 2015 CA. ALL RIGHTS RESERVED.
Owner of Non-
Functional
Requirements

15. 15 © 2015 CA. ALL RIGHTS RESERVED.
Non-Functional Requirements…to name a few
• API Definition
• API Management
• API Versioning
• High Availability
• Scalability
• Diagnosability
• Logging
• Monitoring and Metrics
• Accessibility
• Auditability
• Identity Management
• Provisioning
• Deployment
• Certification
• Disaster Recovery
• Exploitability
• Interoperability
• Maintainability
• Extensibility
• Role Based Access Control
• Security Policies
• Network Security
• Performance
• Reliability
• Resilience
• Portability
• Privacy
• Supportability
• Testability
• Usability
• Backup and Recovery
• Patching and Upgrades
• …and more…

16. 16 © 2015 CA. ALL RIGHTS RESERVED.
Defining
Architecture
and
Technology
Roadmaps

17. 17 © 2015 CA. ALL RIGHTS RESERVED.
Architecture Definition
• Context “Overview” Diagrams
• System “Network” Topology
• Container “Server” Architecture
• Component “Functional” Architecture
• Module Interactions (Class Diagrams etc.)
• Design Specifications, API Standards, Integration Approach
• Glossary … because communication matters!

18. 18 © 2015 CA. ALL RIGHTS RESERVED.
Simple LAMP Stack – Three Tier Web Application
§ From Adrian Cockcroft’s Spigo app –LAMP stack
ELB
WS DB
memcached
DB

19. 19 © 2015 CA. ALL RIGHTS RESERVED.
Single Region Multi-Zone HA Topology – Netflix pattern
ELB
Storage
Storage
Storage
Proxy
Proxy
Proxy
Cache
Cache
Zone A
Zone B
Zone C
Availability Region
Login Page Home Page
Login Page Home Page
Multi-zone
Cassandra
Cluster

20. 20 © 2015 CA. ALL RIGHTS RESERVED.
Server Architecture – Oracle Cloud Applications
§ From Oracle Enterprise Repository: https://fusionappsoer.oracle.com/oer/custom/trm/reference_topology.gif

21. 21 © 2015 CA. ALL RIGHTS RESERVED.
Technology
Evaluation,
Competitive
Awareness,
Incubator
Projects

22. 22 © 2015 CA. ALL RIGHTS RESERVED.
Technology is Changing and it’s not going to wait for us
• Cloud Computing – IaaS, PaaS, SaaS, iSaaS, iPaaS, aPaaS, mBaaS
• DevOps – Continuous *Everything*, *Everything* as Code
• Microservices Architectures, Cloud Native Architectures
• Containers e.g. Docker, Rocket, Kubernetes, AWS Lambda etc.
• NoSQL Databases vs. RDBMS, Agent-less technologies etc.
• Open Source Software and its ramifications

23. 23 © 2015 CA. ALL RIGHTS RESERVED.
See the Big
Picture!

24. 24 © 2015 CA. ALL RIGHTS RESERVED.
Complexities in Modern Web Scale Cloud Apps
§ Firewalls, Security Groups
§ External/Internal Load Balancer VIP
§ External/Internal Routing, Subnets
§ Single Sign-on / Federated Access
§ Security Policies, SSL Certificates
§ Outbound HTTPS Proxy
§ Virtual Private Cloud
§ Identity (Tenant) Management
§ Database Service
§ Messaging Service
§ Storage Service
§ Caching Service
• Best Practice “12 factor” applications
• App Clustered Configuration for HA
• App Configuration for Network
• App Configuration for Security/Identity
• App Association with other services
• Patching: Auto, Locked Mode
• Upgrades: Auto, Locked Mode, Manual
• Data Backup and Recovery
• System Point-in-Time Recovery
• Tenant On-boarding
• Tenant De-provisioning w/ Termination
• Tenant Data “Takeout” / Export
• Tenant Customer Support Console
• Tenant Metrics
• Cloud Portal for Ordering
• Service Metering
• Service App Marketplace
• Service order up-sizing
• Service infrastructure updates
• Service Proxy/Discovery Service
• Service Health-checks
• Service Diagnostics
• Service Logging and Analysis
• Service Monitoring and Metrics
• Elastic Scale-out and Scale-in
• Environment Host Provisioning
• Golden Image Baking / Maintenance
• …and more…

25. 25 © 2015 CA. ALL RIGHTS RESERVED.
You did not mention coding! Do Architects Code?
As much as they need to fulfill their mission - from all the time to wanting to all the time!

26. 26 © 2015 CA. ALL RIGHTS RESERVED.
But wait,
there’s
more!

27. 27 © 2015 CA. ALL RIGHTS RESERVED.
The “Soft” Skills and Experience differentiate the
Architects from Senior Engineers
§ Leadership in technical guidance, decisions, authority
§ Team collaboration, coaching, mentoring
§ Review processes, historical archive, cross pollination
§ Negotiating skills
§ Evangelist, help pre-sales close deals
§ QA for ensuring standards compliance

28. 28 © 2015 CA. ALL RIGHTS RESERVED.
Be Flexible to Adapt to the Culture!

29. 29 © 2015 CA. ALL RIGHTS RESERVED.
Questions?

30. Chief Architect, APM VP, Business Unit Executive, API Mgmt
Michael.Walker@ca.com Rajesh.Raheja@ca.com
Michael Walker Rajesh Raheja
@MichaelWalker @RahejaRajesh
Slideshare.net/mwalker Slideshare.net/rraheja
linkedin.com/in/mwalker11 Linkedin.com/in/rraheja