1. Redis as a job queue (deployed on Oracle Cloud Infrastructure Classic), and
2. a Java based service which acts as a asynchronous processor (a.k.a Worker) deployed to Oracle Application Container Cloud
Worker applications ?
Traditionally, any service deployed to Oracle Application Container Cloud was was required to bind to
$PORT and was given a public URL. But this is actually not required for all kinds of workloads/app types — so you were forced to do things like expose a REST endpoint for a batch processing app ( I know I have ;-) )
Worker applications were built to tackle these kind of problems (and more) and they differ from traditional ACCS applications. Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.
Don’t Miss these Oracle OpenWorld 2018 PaaS Sessions! Developer Partner Community For regular information become a member in the WebLogic...