Open kwsutter opened 6 years ago
If we find that this doesn't fit into the guide criteria - simple, self-contained, < 30 mins, etc. We could consider doing it as a code pattern on IBM Developer.
I am not sure if we can fit what's needed under 30 mins either. Yes, we can do it as a code pattern or publish there too.
I think we should take this opportunity to prototype and see what will a track look like and go from there. I suspect what we need here goes beyond the usual guides that we currently have but can be built upon them.
@cajaygle @megmulsy
I'd like to see this published as a guide. I know we're trying to keep guides short, but if we're pointing people to OpenLiberty.io, and then have them shell out to IBM Developer, I do not like that.
I heard this request from people at EclipseCon Europe when we did our https://www.eclipsecon.org/europe2018/sessions/developing-cloud-native-java-microservices-eclipse-microprofile talk. I absolutely agree we need a more comprehensive (or 'advanced' as the attendees suggested) series of guides.
This could be a single guide, or multiple guides. It would make sense to have a guide tied to the TO-BE examplar on https://github.com/gothinkster/realworld.
We need to figure out whether this should be a code pattern, part of the quick labs/tutorial, a track, or combination/variation of them.
Copy @lauracowen in case she has thoughts.
This sounds like what ID used to call a 'showcase scenario' (as distinct from a tutorial etc in that it demonstrates multiple capabilities at once in a more realistic scenario). I understood it that to be something along the lines of Red Hat's Ticket Monster app, which I always liked the idea of: https://developers.redhat.com/ticket-monster/
Fwiw, nothing that we do have https://github.com/ibm-cloud-architecture/refarch-cloudnative-kubernetes/, which has a MP implementation.
I'm looking for a guide that would show how some (most? all?) of the MicroProfile components could work together within an application or microservice. One of the first guides developed showed how to develop a simple microservice using the basic MicroProfile Java EE components (jax-rs, jsonp, and cdi). Since that time, we have focused on the simple single component approach to MicroProfile (ie. Config, Fault Tolerance, Metrics, etc). This is all good stuff and very necessary. Makes for an easy introduction to the various components.
But, now I have some developers asking for more comprehensive guides. How could the various MicroProfile components be used together to accomplish various goals or scenarios? For example, how could one use Metrics for monitoring some of the other components (ie. Fault Tolerance)? Or, using Config for defining the configuration for JWT? Maybe this would eventually break down into multiple Issues. Just wanted to start the conversation about developing more involved guides for MicroProfile.