1. [CITY] MuleSoft Meetup Group
Journey

2. 2
● Introductions
○ Selection process
○ Implementation
○ Architecture
○ Challenges
○ KPIs, Store, Re-use
● Networking time
Agenda

3. Presenters
• Name: Robert Bruns
• Title: Director of Application Development for
the City and County of Denver
3
• Name: Nate Kresse
• Title: Integrated Application Development Manager
for the City and County of Denver

4. Selection Process

5. 5
Technology service currently hosts 150 integration components on Oracle SOA Suite. In reviewing all integrations and
current feature sets Technology Services developed 32 integration platform requirements categorized in five areas:
 Infrastructure requirements
 Developer tooling and features
 Enterprise integration capabilities
 Governance capabilities
 Security
● Main consideration
 Out-of-the-box as much as possible
 Ability to use CI / CD pipelines
 Enterprise integration pattern support
 Automated testing with Katalon
 Self-documenting APIs
 KPI dashboard that can be segmented and shared
 Hybrid model
 Reuse
Evaluation Criteria

6. Implementation

7. 7
Hybrid Environment – Software Development Lifecycle
○ Server provisioning: DEV,TEST, QA, PROD
○ CI/CD setup
○ Commons library for code reuse
○ Exchange documentation
○ Cloud custom networking approach
○ Automated testing with Katalon
Governance
○ Data reviews
○ Standard API policies
○ Automated client requirement in build
○ Code reviews on merge
○ Approvals on deployment
Initial Build Out

8. 8
Follow Best Practices! (Part of the Architecture training)
Cloud Architecture

9. CCD’s API-Led Adoption Journey
9

10. Alignment to Strategic Plan
10

11. ● Reliability
○ Fast incident resolution
○ Metric dashboards
● Innovation
○ Advanced queuing and reliability patterns
○ Rapid API deployment
● Access
○ Vendor API access
○ Partner developers’ client access
● Partnership
○ Exchange documentation reduces ramp uptime
○ Enterprise integration patterns
11

12. Roadmap
12

13. Challenges

14. Challenges
● Went on-premise vs. cloud-based on security concerns
● Queuing on-premise with RabbitMQ
● Analysis of existing SOA code
● Testing bottlenecks
● Complexity of test scenarios when many systems/user groups
● A la cart options for architecture instead of a best practices approach
● Getting an AWS direct connect/VPN setup
14

15. Highlights / Common Questions
● On-prem vs Cloud deployment criteria
● Support process and dashboards
● Visual KPIs
● SDLC lifecycle: CI/CD and code reviews
● 32% reuse and speed of delivery
15

16. 16
● Share:
○ Tweet using the hashtag #MuleSoftMeetups
○ Invite your network to join: <URL of your Meetup site>
● Feedback:
○ Fill out the survey feedback and suggest topics for upcoming events
○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program
What’s next?

17. Introduce yourself to your neighbor
Networking time

18. Thank you