Unfortunately the openjdk version zulu-11 seems not to bee supported yet and I used oracle jdk 11 instead. I want to keep an eye on it so that I can change it as soon as possible. see article on Heroku and Java versions

Should then be working like this

@mle-enso when I try to execute this test, eclipse tells me this:

Could not resolve artifact org.springframework.boot:spring-boot-dependencies:pom:2.0.0.M3
Missing org.springframework.boot:spring-boot-dependencies:pom:2.0.0.M3

Is there a problem with Spring Boot 2.0.0.M3 and testNG or did I miss anything else?

see also:
https://www.slideshare.net/ewolff/four-times-microservices-rest-kubernetes-ui-integration-async
https://github.com/ewolff/microservice
https://spring.io/guides/gs/service-registration-and-discovery/

…by using https://codecov.io as can be seen here https://github.com/mle-enso/turing-machine

I am pretty sure that we already had a show case of SSE in one of our controllers. This is no longer the case.
I would love to see such an endpoint may be similar to this one
@GetMapping(path = "/entries", produces = MediaType.APPLICATION_JSON_UTF8_VALUE)
but behaving with real SSEs
@GetMapping(path = "/entries", produces = MediaType.APPLICATION_STREAM_JSON_VALUE)

so that entries cannot be deleted too easily.

use spring security

Evaluate router functions for reactive endpoints and try them out as alternative way as described in this article: https://dzone.com/articles/spring-boot-reactive-tutorial

Ever since mvn clean verify has been made obligatory for a deployment in heroku, with each deployment two Entry items ("LINUX Waschmittel") are written into the live db. This shouldn't happen.
Either the item must be deleted again after creation - or there is a possibility to use another db during the deployment verify process.

Offer possibility to change name, URL and category of an existing Entry

Implement an aspect that logs method execution times for all public methods in your controller classes.

The showAllEntries test still is disabled, which also means that its REST documentation doesn't work.

The error message says

Cannot handle text/html content as it could not be parsed as JSON or XML

How to solve this in a reactive way?

rememberbrall.heroku.com is currently live with the latest commits you can see in the branch mongodb: https://github.com/evainga/rememberbrall/tree/mongodb
This works in heroku live version, however, the travis build failed as well as local builds fail. This is because i out commented spring.data.mongodb.database=demo to make spring.data.mongodb.uri=${MONGODB_URI} work for heroku.

So, which mongo should ideally interact on which stage with rememberbrall? Would it be good to use the same database for different stages - local, travis (=testing?) and in heroku (=production)? Because currently, the placeholder I use in heroku is not known locally and in travis.

Description:
Binding to target [Bindable@1cf0cacc type = java.lang.String, value = 'provided', annotations = array[[empty]]] failed:
Property: spring.data.mongodb.uri
Value: ${MONGODB_URI}
Origin: class path resource [application.properties]:7:25
Reason: Could not resolve placeholder 'MONGODB_URI' in value "${MONGODB_URI}"

Or - if every stage should have their own database (which I think they should), then the better question is: How can I define the distinction for the stages in application.properties?

Codacy currently reports at least one new potential code flaw...
https://www.codacy.com/app/evainga/rememberbrall/issues/index?&filters=W3siaWQiOiJDYXRlZ29yeSIsInZhbHVlcyI6WyJDb2RlIFN0eWxlIl19XQ==

static final String LINUX_WASCHMITTEL = "Linux Waschmittel"

This is only an example... keep an eye on all your reports... codacy, codecov, whatever will be added in the future and fix all items as soon as possible. This prevents cumulation of a huge load of technical debt.

The Heroku URL answers with a "Whitelabel Error Page" instead of a welcome page of your server.

some ideas wich have not been prioritised

• Change entry
• Sorting
• Multiple categorys for same entry
• connection to browser bookmarks

see https://github.com/meistermeier/reactive-thymeleaf

Add function delete all entries - maybe with some additional security features

https://wiki.eclipse.org/Configure_Eclipse_for_Java_9

No this is not correct, integration tests should be executed by the maven-failsafe-plugin.
Refer also to its documentation https://maven.apache.org/surefire/maven-failsafe-plugin/examples/inclusion-exclusion.html
General mantra: fast running (unit) tests are covered by surefire, long running (integration) tests by failsafe. Please switch this line to the failsafe plugin config.

Study the following article: https://www.callicoder.com/reactive-rest-apis-spring-webflux-reactive-mongo/

…and answer the following questions:

Question 1: What are Server Sent Events?

Question 2: Try the following curl requests and answer: What is the fundamental difference between the following to requests to your Rememberbrall server:

• curl https://rememberbrall.herokuapp.com/entries -H "Accept: application/json"
• curl https://rememberbrall.herokuapp.com/entries -H "Accept: application/stream+json"

Question 3: Why is the second curl request above not appropriate for clients which rely on well-formed JSON data?

…by using https://www.codacy.com as can be seen here https://github.com/mle-enso/turing-machine