Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create second quarkus sample app #11

Closed
hohwille opened this issue Aug 6, 2021 · 2 comments · Fixed by devonfw-sample/devon4quarkus-order#1
Closed

Create second quarkus sample app #11

hohwille opened this issue Aug 6, 2021 · 2 comments · Fixed by devonfw-sample/devon4quarkus-order#1

Comments

@hohwille
Copy link
Contributor

hohwille commented Aug 6, 2021

With #8 , #9 and #10 we want to improve our first sample app for quarkus.
When this is done, we want to create a second app with this story:
The idea is to create a second app:

  • repository: devon4quarkus-order
  • component name ordermanagement
  • entities Item and Order - general idea from here, however using MonetaryAmount for price (see Change quarkus reference app from animals to products #9). Why are attributes like price stored redundantly? The price in the master-data (productmanagement) may change but that shall not change the history of existing Orders that have already been paid. Same for title (called name in the linked UML diagram). Do not copy details such as description from product. Also add productId as property to Item. As this is pointing to an entity from a different service/app, it can not be a foreign key constraint but is just a long number.

In order to create an Item for a given product-ID this app shall use quarkus rest-client to get the product data and fill according properties in the item. Things like creationDate shall be auto-populated by use-case (Instant.now()).

As discussed in #6 we should also demonstrate a REST service that gets generated from an OpenAPI contract. We could generate the OpenAPI contract for our product service (see devonfw/devon4j#216). Then we could include this OpenAPI file here and generate the REST API code artefacts for the quarkus-rest-client from it automatically.

@GuentherJulian
Copy link
Contributor

@lilliCao Hey team! Can you please add your planning poker estimates with ZenHub

@Przemek-Majtyka
Copy link

Please add your planning poker estimate with ZenHub @TugbaDalmaz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants