Helidon MP 2.0 Intro #1653
Merged
Helidon MP 2.0 Intro #1653
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ljamen
changed the title
|
This is a new topic to head up the new MP section of the doc. In 2.0 the docs were split into MP and SE. |
ljamen
changed the title
46 tasks
Doc updates 1628 intro hmp
|
This PR is for the MP introduction and the getting started located in mp/introduction. @m0mus |
m0mus
approved these changes
Jun 4, 2020
|
|
||
| Helidon MP is an implementation of the | ||
| Helidon MP {helidon-version} is an implementation of the |
There was a problem hiding this comment.
It doesn't make sense adding a version number here. It's about Helidon MP in general.
|
|
||
| For comparison, the high-level differences between Helidon MP and Helidon SE are described below. | ||
|
|
||
| [width="100%",options="header"] |
There was a problem hiding this comment.
The table is too long. It looks like word wrapping is not supported when we render a table. Try adding soft line breaks or maybe Daniel will be able to fix it in the renderer itself.
| * MicroProfile JWT Authentication | ||
| * MicroProfile Metrics | ||
| * MicroProfile OpenAPI | ||
| * MicroProfile OpenTracing | ||
| * MicroProfile Rest Client | ||
|
|
||
| For more information see <<guides/01_overview.adoc,guides>>. | ||
| For more information about the Helidon MicroProfile APIs see https://github.com/oracle/helidon/wiki/Supported-APIs[the Helidon API Wiki page]. |
There was a problem hiding this comment.
Does it make sense moving it from the wiki to the docs?
| === MicroProfile Reactive Messaging and Reactive Streams Operators | ||
| Asynchronous messaging is a commonly used form of communication in the world of microservices and the Reactive Messaging for MicroProfile specification is a logical response to formalizing the ways we connect things together. And the best way to communicate asychronously is through Reactive Streams. With the release of the MicroProfile Reactive Streams Operators specification we can now formalize manipulation with reactive streams. Reactive messaging heavily depends on standardized operators so together they provide great portability between existing implementations. | ||
|
|
||
| <<link to MP Messaging/Streams topic>> | ||
|
|
||
| == Try it now | ||
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.