...
In the table below you can see the pros and cons:
Implementation | Pros | Cons | Main purpose |
|---|---|---|---|
App & Low Code, Pipelines | Easy to learn. No deep developer skills required. Very fast results possible. No compilation and build steps required. Huge set of out-of-the-box toolings like forms, lists, reports and utils available. Based on many pre-defined standards which can simplify maintenance and upgrading. | Limited to its main purposes. Requires a deployment process. | For data mappings and transformations, workflows and system integrations. Building frontend apps with forms, listings and basic reports. |
Microservice | Very flexible: You can use any programming language and libraries of your choice and you can develop any business complexity you like. | Requires developer skills and somebody who reviews and manages the architecture of the microservice. Requires a build and deployment process. | For complex business logics, running mainly as background services. |
It's also possible to combine apps and microservices in order to implement a single business solution:
...
These implicit variables are:
ENV | Description |
|---|---|
|
...
The domain name used for the PIPEFORCE instance. For example | |
|
...
| The cluster internal |
...
host name of the hub service in order to connect to. |
|
...
| The cluster internal host port in order to connect to. |
|
...
| The cluster internal url of the hub service in order to connect via REST for example. |
|
...
| The default dead letter queue used for RabbitMQ messaging. |
|
...
| The default |
...
messaging exchange used for RabbitMQ messaging. |
|
...
The default messaging topic used for RabbitMQ messaging. |
...
It is usually the same as the default exchange. | |
| The messaging host to connect to in order to register a RabbitMQ listener. |
| The messaging host to connect to in order to register a RabbitMQ listener. |
| The namespace of the instance this services runs inside. |
| The external url to the PIPEFORCE webui portal in order to refer to from inside a microservice. |
| The name of this custom service inside PIPEFORCE. |
| The staging mode, this namespace is running in. Usually one of |
Additionally to these default environment variables, you can also set add your custom ones by using the parameter env on the command service.start:
...
See here for more details about message key patterns on topics: https://www.rabbitmq.com/tutorials/tutorial-five-python.html
Message / Event Key | Description |
|---|---|
| In case a new delivery was created. |
| In case a new public link for a delivery was created. |
| In case a public link for a delivery has been deleted. |
| In case the attachments of a delivery have been deleted. |
| In case the deletion of the attachments have been failed. |
| In case hub has context has been started is ready to accept requests but right before the startup phase. |
| In case hub context is about to start. Note: This event is not send to the topic queue since at the time of this, the RabbitMQ connector is not setup yet. This event is just for internal use in hub. Its mentioned here just for completeness reasons. |
| In case hub setup has been finished. |
| In case the hub setup is about to be started. This is right after the context has been started but before the setup has been fully finished. |
| In case a potential bruteforce attach has been detected by IAM. |
| In case a login using IAM has been failed. |
| In case a property in the property store has been copied. See PropertyCopiedEvent.java for implementation details. |
| In case a property in the property store has been created. See PropertyCreatedEvent.java for implementation details. |
| In case a property in the property store has been deleted. See PropertyDeletedEvent.java for implementation details. |
| In case a property in the property store has been moved. See PropertyMovedEvent.java for implementation details. |
| In case a property in the property store has been moved. See PropertyUpdatedEvent.java for implementation details. |
| A new usagelog entry was created in the property store. See UsageLogCreatedEvent.java for implementation details. |
| In case a webhook call has been occurred. The <name_of_webhook> depends on the setup. You can use the pattern webhook.# to listen to all webhooks. |
Depends on key param of command event.send. | Furthermore whenever the command event.send is called, the payload of this event is also forwarded to the default hub topic using the key param of this command as the messaging key and the body as the payload of the message. |