Deploy Appian Application ZIP File and Patch as a Microservice onto a container

RE: Deploy Appian Application ZIP File and Patch as a Microservice onto a container

aneeshv713 — Thu, 11 Jul 2019 20:42:26 GMT

All I am asking is a pretty simple question. In Other BPM products especially some open source products , the end product or end application that is built is a deployable WAR file which can be compiled as a microservice to a container and deployed . Can the same be done to Appian ‘s Application ZIP File or Patch?

RE: Deploy Appian Application ZIP File and Patch as a Microservice onto a container

Eliot Gerson — Thu, 11 Jul 2019 20:28:03 GMT

Again, in order for something to be a "microservice" , it has to first be a service--it has to be able to run. An application package isn't something that can be run. I realize the term "application" has become a bit overloaded these days, but in Appian terminology, an application is a container that holds Appian objects. It's a way to organize your development, and it may correspond to business cases that you're trying to solve. But it's not an "application" in the sense of a program that you run on your computer, like Microsoft Word or Adobe Photoshop.

Maybe it would help if you explain or give an example of the problem you're trying to solve.

RE: Deploy Appian Application ZIP File and Patch as a Microservice onto a container

aneeshv713 — Thu, 11 Jul 2019 20:18:43 GMT

I understand what you are saying. Actually an Appian Application ZIP File is a bunch of files wrapped into a zip file and Appian kind of auto compiled before the export. That’s why a non compile pipeline can be used in CICD . But what if we want to still deployas a non compilable microservice kind of to mimic something which we can do with plugins or connected systems deployment? Is that even possible?

RE: Deploy Appian Application ZIP File and Patch as a Microservice onto a container

Eliot Gerson — Thu, 11 Jul 2019 20:00:42 GMT

I'm not sure the question really makes sense. A application zip or patch isn't a service; there's nothing executable about it. So "deploying as a microservice" isn't really an applicable concept.