Implement user story demonstrating how Ship.Cars utilizes Quarkus to achieve objectives #1937
Conversation
ivelinyanev-ship-cars
force-pushed
the
develop
branch
from
74c40b8 to
a4f72e9
Compare
|
Hi @maxandersen This pull request requires your attention. If it's not possible for you to review it at your earliest convenience, could you kindly delegate the task to someone else on the team? Thanks for your cooperation |
|
Hey, sorry for the delay. Having a look now :). |
There was a problem hiding this comment.
Very nicely written, thanks!
I made some very small adjustments to uncapitalize the titles as that's our new convention.
Also also fixed what I think is a small typo.
(I pushed to your branch so make sure you pull from your fork before editing things)
Apart from that, it's a very nice post, I just added a small question. I'm fine with it even if you think you don't need to add something, let me know.
| These escalate gradually as we advance along the timeline towards _"Middle"_ and _"Future"_, showing a tangible increase in productivity and other gains from adopting and integrating Quarkus features into our practices. | ||
|
|
||
| By the time we reach _"Future"_, we see a substantial decrease in difficulty and cost, while the ease-of-use and returns have considerably increased. | ||
| This dual progression effectively highlights the significant benefits of investing in the adoption of Quarkus, despite the initial challenges. |
There was a problem hiding this comment.
Was the initial challenge because Quarkus is hard to grasp or because you were coming from Spring Boot/Django and so were not in known territories as you needed to learn Microprofile/Jakarta EE/...?
Because I wouldn't expect the switch to Quarkus being hard if you're relatively familiar with the technology?
Anyway, maybe worth a mention if you think it makes sense.
There was a problem hiding this comment.
Hi @gsmet
Firstly, I appreciate your comments.
I'd like to share an insight based on feedback from my colleagues, suggesting that an in-depth understanding of the standards is needed, specifically around native code execution. This necessitates a comprehensive understanding of native compilation principles, as well as a more detailed understanding of how Quarkus and Graalvm operate.
Additionally, we've developed a robust set of custom extensions. For this, I found it necessary to provide training on creating such extensions. However, I agree with the perspectives conveyed in the graphic. It's indicative of the fact that acquiring a thorough command over Quarkus's capabilities does necessitate a significant personal commitment.
Thank you.
|
🙈 The PR is closed and the preview is expired. |
|
ivelinyanev-ship-cars
force-pushed
the
develop
branch
from
a198619 to
c2f2319
Compare
|
Nice read, cool! |
|
Thanks for your contribution: it's now live: https://quarkus.io/blog/ship-cars-leverages-quarkus-to-reach-its-goals/ |
No description provided.