After looking into how to run a Spring-Boot based Microservice application on Oracle’s Application Container Cloud service, this post will concentrate on Oracle Container Cloud Service. In short, Oracle Container Cloud Service is Oracle’s enterprise-grade container infrastructure solution. It provides features to compose, deploy, orchestrate and manage Docker container-based applications. In contrast to Oracle Application Container Cloud Service customers can completely control containers deployed within this infrastructure. Therefore, this service provides the highest amount of flexibility for container-based applications. On the other hand, it does not relieve customers of tasks like Oracle Application Container Cloud Service.
The worklist application is the out of the box user interface of the human workflow engine. It allows users to view their pending tasks and work on them with the help of custom ADF Views. One important additional feature of the worklist application is the possibility to define rules that change automatically the task assignment if some conditions are met.
In posts one and two within this series we created and deployed Spring-Boot Microservices in Oracle’s Application Container Cloud Service (ACC). Usually, after deploying an application and enabling user traffic an application must be monitored to ensure a high level of service and identify approaching problems. This blog post describes how monitoring in Oracle Application Container Cloud can be achieved using standard features. The focus will be on Java applications.
In this blogpost I would like to show you, how an EC2 instance can register itself automatically on AWS Route 53. This could be important, if you have ie. a clustered group of nodes (like an Apache ZooKeeper or Kafka Cluster) where a list of DNS-Names or IP-Addresses need to be configured and you don't want to use AWS specific DNS names.
In my last post I gave an introduction to Oracle Application Container Cloud (ACC) and how to develop Spring-Boot applications such that they can be hosted within Oracle ACC. At the end of the post some questions still had to be answered. Within this post we are going to tackle the first one, how is Microservice Communication in Oracle Application Container Cloud achieved? The following figure shows what a simple architecture, within the context of a Spring-Boot Microservice application, might look like.
Microservices as an architectural style as well as scalable and manageable cloud infrastructure are the foundation for modern and flexible business applications. Therefore, Oracle invested heavily in maturing its Cloud portfolio and providing services to support development and operations of such applications. One Oracle cloud service aimed at these kind of applications is “Oracle Application Container Cloud Service” (ACC). It provides a simple Docker based environment in which your Microservices can be deployed. In order to reduce the operations overhead, developers only have to provide their applications (NodeJS, Java SE or PHP) in a certain format and Oracle’s cloud infrastructure takes over.