A few days ago I had an interesting discussion with my wife which made me think about processes and culture again. To understand my reasoning one has to know that my wife is a classic business person. She has several business degrees and is a consultant working as project and process manager focusing on process optimisation and automation for several large clients. Within this area most people in her role will likely interact with IT departments and inevitably get into contact with some agile development process. As agile processes and principles are somehow disconnected from what most business students and professionals learn regarding project management, my wife got serious about the topic and took part in an agile training. Our discussion started after this training. Within this blog post I want to share my two takeaways regarding agile culture I gained from this discussion.
Every now and then you might want to store some configurations in simple configuration files and use them as OSB Resources in pipelines. In most cases OSB functionality is sufficient to fulfil your requirements. However sometimes you might not be able to get to your goal directly. Recently, I had to retrieve a list of all values in a specific domain column within a Domain Value Map (DVM). As DVMs are primarily used to map one domain value to one or multiple other domains, existing DVM functions do not provide the capability to retrieve all values from a domain column. Therefore, I developed a Java Callout to get the desired result. The solution is applicable to all OSB resource types. This blog post presents the basic concepts used to implement a solution.
Within my last post the Camunda Spring-Boot Starter application used a h2 in-memory database. In general this is a good approach while developing and testing, but it should be replaced by a persistent database in later development and production stages. Using Spring-Boot capabilities this can be easily achieved by configuration. Within this post we will create a Camunda Spring-Boot starter database configuration which uses h2 in-memory database during automated tests only. For all other scenarios a MySQL database is used.
Der Artikel Camunda Spring-Boot Starter Database Configuration erschien auf esentri AG - Oracle Gold Partner.
In previous posts we discussed how Microservice applications can be implemented, combined and monitored in Oracle Application Container Cloud service. So far, we focused on a manual deployment process. However, when aiming to implement a working Microservice strategy DevOps is a key success factor. One area DevOps concentrates on is software delivery automation (CI/CD).
Der Artikel Deploy to Oracle Application Container Cloud using Maven erschien auf esentri AG - Oracle Gold Partner.
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.
Der Artikel Running Spring-Boot Microservices on Oracle Container Cloud erschien auf esentri AG - Oracle Gold Partner.
Vor ein paar Tagen bin ich auf den Blog-Artikel "Agile Mythen: User Stories schreiben ist Product Owner Aufgabe" von Anna Rudat gestoßen. Als Enthusiast der agilen Softwareentwicklung und Product Owner Veteran, wurde ich mit der Meinung, dass allein der Product Owner für das Schreiben der User Stories allein verantwortlich ist, schon häufig konfrontiert. Nachdem ich den Artikel gelesen hatte, erinnerte ich mich an meinen letzten Einsatz als Product Owner und wie mein Team und ich uns in dieser Hinsicht geschlagen haben.