Introductional blog post - base content #2273
Conversation
MichalMaler
force-pushed
the
mmaler-bog-post-intro
branch
from
cdb3078 to
7ef384d
Compare
|
🎊 PR Preview febfd0f has been successfully built and deployed to https://quarkus-site-pr-2273-preview.surge.sh
|
MichalMaler
force-pushed
the
mmaler-bog-post-intro
branch
2 times, most recently
from
d820e59 to
edd2002
Compare
Basic info Adding tags Signed-off-by: Michal Maléř <[email protected]>
MichalMaler
force-pushed
the
mmaler-bog-post-intro
branch
from
edd2002 to
1007bd4
Compare
|
@gsmet @maxandersen @cescoffier @aloubyansky Hello! Would you happen to have anything we can add or improve? Cheers! |
| Quarkus successfully deployed 10 APIs across 4G/5G network cores, with smooth upgrades and optimized resource usage. | ||
| This solidified Quarkus as a key technology for telecom innovation. | ||
| + | ||
| For a collection of user stories from the community, see the Quarkus user stories blog series. These stories highlight how different teams and organizations are using Quarkus in the real world. |
There was a problem hiding this comment.
put a link to https://quarkus.io/userstories/ ?
| === Versatile build tool integration | ||
|
|
||
| Quarkus integrates with popular build tools like Maven and Gradle, making adoption in many existing development workflows easier. | ||
| Maven users benefit from first-class support, while Gradle users can build Quarkus projects with the help of community-maintained tooling, though it currently lacks feature parity with Maven. |
There was a problem hiding this comment.
it is both community maintained from context of quarkus.io community blog so I would just leave this out imo
|
|
||
| === Panache 2: Simplifying data access | ||
|
|
||
| Hibernate ORM with Panache is a lightweight abstraction layer built on top of Hibernate ORM that simplifies data interactions and reduces boilerplate code. |
There was a problem hiding this comment.
cool to mention this but without code or some examples this to me does not provide much value to a reader ? its a lot of positive words for sure; but what have the reader learned after reading this?
| For example, the Spring compatibility layer allows reuse of familiar annotations and patterns, see the link:https://quarkus.io/guides/spring-di[Spring DI guide] to learn more. | ||
|
|
||
| And if you need help? You’re not alone. | ||
| Quarkus experts, like Roberto Cortez, can visit your company, demo what Quarkus can do, and guide you through the entire migration process—from architecture review to production readiness. |
There was a problem hiding this comment.
@radcortez you wanna be called out to come and visit ? :)
Is this really something we want to push on quarkus.io community site ?
There was a problem hiding this comment.
Many on the Quarkus team also do that work. I can see that it can pass as being the work of a single person when it is not. I think it would be better to remove it.
| layout: post | ||
| title: 'Optimizing Java for the Cloud-Native Era with Quarkus' | ||
| date: 2025-03-31 | ||
| tags: introduction development reactive performance java cloud |
There was a problem hiding this comment.
just pick one or two tags. the tag UI gets overloaded with all these. yes, problem in others too and on my todo to get cleaned up ;)
|
|
||
| === Developer joy with live coding and dev mode | ||
|
|
||
| Quarkus revolutionizes the development workflow with its live coding feature. |
There was a problem hiding this comment.
We should probably tune this down a bit since this was possible before, to some extent, using paid tools (JRebel).
| By optimizing for low memory usage and fast startup times, Quarkus enables higher-density deployments and rapid scaling. | ||
| This efficiency leads to significant cost savings in cloud environments as resources are used more effectively. | ||
| Companies looking to reduce cloud costs while maintaining high performance will find Quarkus an excellent solution. |
There was a problem hiding this comment.
We should probably say that for the same comparable workload, we expect Quarkus to use fewer resources (CPU / Memory), but that users / companies looking to make the change, should always measure the workloads.
|
|
||
| === Reactive at its core | ||
|
|
||
| At its core, Quarkus is built on Eclipse Vert.x, a high-performance reactive toolkit. |
There was a problem hiding this comment.
How about some code here as an example?
|
|
||
| == Which of your current development pains could Quarkus solve effortlessly? | ||
|
|
||
| In general, Quarkus will save you a lot of time and money as well as CPU and memory resources. |
There was a problem hiding this comment.
We already implied this in the above section.
|
|
||
| === Vast extension ecosystem | ||
|
|
||
| Quarkus offers a rich extension ecosystem that simplifies integration with essential technologies such as databases, messaging systems, authentication providers, and cloud services. |
There was a problem hiding this comment.
We should also mention Quarkiverse.
| With Quarkus, the transition doesn’t have to be painful. | ||
| Thanks to its compatibility with existing Java standards, support for Jakarta EE and Spring APIs, and an extensive extension ecosystem, many projects can migrate incrementally, without rewriting everything from scratch. | ||
| For example, the Spring compatibility layer allows reuse of familiar annotations and patterns, see the link:https://quarkus.io/guides/spring-di[Spring DI guide] to learn more. |
There was a problem hiding this comment.
While we know that many users are on Spring, we also want to target non Spring / non Quarkus users, so we probably need to make this a little more inclusive.
Here is the first blog post I created for the Quarkus Evangelism mission created during the Brno F2F.
The purpose of the file is to summarize why Quarkus is so great and how anybody should try it out and then, ofc, migrate to it :)