Download as PDF, PPTX
Uploaded byAtlassian
"Hacking" JIRA and Confluence Cloud Part 1 - Connect Your Apps - Travis Smith
The document discusses integration patterns for Jira and Confluence using direct and indirect connections, highlighting their pros and cons. It emphasizes features such as real-time communication, the complexity of maintenance, and the importance of data loads. Resources for further information on integration frameworks and related concepts are also provided.
More Related Content
Similar to "Hacking" JIRA and Confluence Cloud Part 1 - Connect Your Apps - Travis Smith
![[Customizable Template] How to Get Stakeholder Buy-In for a Toolchain Integra...](https://cdn.slidesharecdn.com/ss_thumbnails/ppttemplate-howtogetstakeholderbuy-inforanintegrationplatformsv-230517182937-82cc41ed-230518162035-f0383f02-thumbnail.jpg?width=640&height=640&fit=bounds)
![[오픈소스컨설팅]Session 2 1. Future of Team Collaboration](https://cdn.slidesharecdn.com/ss_thumbnails/session2-1-161124041116-thumbnail.jpg?width=640&height=640&fit=bounds)
![[Customizable Template] How to Get Stakeholder Buy-In for a Toolchain Integra...](https://cdn.slidesharecdn.com/ss_thumbnails/ppttemplate-howtogetstakeholderbuy-inforanintegrationplatformsv-230517182937-82cc41ed-thumbnail.jpg?width=640&height=640&fit=bounds)
"Hacking" JIRA and Confluence Cloud Part 1 - Connect Your Apps - Travis Smith
- 1.
- 2. Travis Smith •Developer Evangelist • Atlassian • @TravisTheTechie JIRA and Confluence Cloud Connect Your Apps
- 3. The stage Integrations JIRA andConfluence Cloud Integrations Patter ns Enablers @TravisTheTechie
- 4.
- 5. The stage Integrations JIRA andConfluence Cloud Integrations Patter ns Enablers @TravisTheTechie
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20. The stage Integrations JIRA andConfluence Cloud Integrations Patter ns Enablers @TravisTheTechie
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37.
- 38.
- 39.
- 40.
- 41.
- 42.
- 43. Direct integration Pros • Lowcomplexity for small systems • Timing is adjustable - realtime or batch events • Can be one way or two communication • Web services are well understood Cons • Easy new system is up to n-1 new connectors • Maintenance harder over time • Requires touching each connecting system when new system brought online
- 44.
- 45.
- 46.
- 47.
- 48.
- 49. Data loads Pros • Cancontrol load • Easier to merge data from multiple sources to answer questions • If multiple events are required for final state, can be calculated at once • Advanced ETL tooling exists Cons • Events are bound to process timing, no realtime events • Not suitable for time critical work • Loads can have performance impact • Limited to one way communication
- 50.
- 51.
- 52.
- 53.
- 54.
- 55.
- 56.
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65.
- 66.
- 67.
- 68.
- 69.
- 70.
- 71.
- 72.
- 73.
- 74.
- 75. Indirect Pros • New systemsrequire one connector, no edits to existing ones • Real time, two way communication • Connectors can primarily be bus to API bridges • Easy to have or introduce coordinators Cons • Messaging requires infrastructure to support it • Multiple events required for final state requires aggregators built into connectors or systems
- 76. The stage Integrations JIRA andConfluence Cloud Integrations Patter ns Enablers @TravisTheTechie
- 77.
- 78.
- 79.
- 80.
- 81.
- 82.
- 83. Frameworks Atlassian Connect Express AtlassianConnect Play!
- 84. Frameworks Atlassian Connect Express AtlassianConnect Play! Atlassian Connect .NET
- 85.
- 86.
- 87.
- 88.
- 89.
- 90.
- 91. More resources eaipatterns.com Enterprise ServiceBus: Theory in Practice connect.atlassian.com go.atlassian.com/acnet
- 92. Travis Smith •Developer Evangelist • Atlassian • @TravisTheTechie Questions?
- 93. Travis Smith •Developer Evangelist • Atlassian • @TravisTheTechie Thank you!