You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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:
ordermanagement
Item
andOrder
- general idea from here, however usingMonetaryAmount
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 fortitle
(calledname
in the linked UML diagram). Do not copy details such asdescription
from product. Also addproductId
as property toItem
. 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 likecreationDate
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.
The text was updated successfully, but these errors were encountered: