Google App Engine is a great environment to get started hosting this sort of solution.
- You just upload code.
- We handle scaling for you.
- App Engine serves up webservices with little to no config.
- App Engine integrates well with other Google Developer Services
On the Atlassian side, as long as you write your services to respond the way Connect expects, you can write your add-ons in whatever language or technology stack you want.
I wrote the Atlassian Connect Add On Starter Kit for App Engine to give a working example for getting started on App Engine using each of the supported languages. Each language folder (Go, Java, Php, Python) contains code to create two applications:
Hello World – basically the Hello World example written by Atlassian with added App Engine configs to show the delta between a vanilla add-on and one configured to run on App Engine.
Language Check – this application scans a JIRA instance for issue titles in languages that differ from the default language, and then labels which language they are. The idea is that you can then easily triage issues that should be routed to staff who can support that language. It takes advantage of the Google Translate API to accomplish this.
Now, all of this isn’t to say you cannot use other technologies in Google Cloud Platform to host your add-on. You can also host on either Compute Engine or Container Engine. After you configure one of these solutions you can just follow Atlassian’s existing tutorials to create an add-on.
Anyway you want to do it, Google Cloud Platform can help the Atlassian developer community to host their applications. If you want to write some code and have server configuration and scaling handled by us, App Engine is a good choice. If you would rather have more control over or flexibility with the systems you run, either Compute Engine or Container Engine can be your answer.
tpryan.blog 