Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,201 @@
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.

"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:

(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.

You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Original file line number Diff line number Diff line change
@@ -0,0 +1,128 @@
# Jakarta EE on Virtual Threads with Helidon MP

This repository reproduces the code and load-test scenarios from the Jakarta EE on Virtual Threads presentation. It contains one Helidon MP 4.4 credit-decision service running familiar Jakarta REST and CDI code on Java 21 virtual threads.

The two demo paths make the runtime story concrete:

- `POST /credit-decisions/evaluate` retains the 65 ms simulated blocking workflow and skips persistence. Use it to isolate virtual-thread scheduling.
- `POST /credit-decisions` runs the same workflow and persists the result to Oracle when OBaaS injects the datasource. Use it to observe the additional JDBC-backed insert and transaction work.

## Repository layout

```text
helidon-credit-service/ Helidon MP application and OBaaS values
load-tests/ k6 scripts for the two presentation scenarios
api/ OpenAPI contract and sample requests
deploy/obaas/ OBaaS deployment and gateway instructions
```

## Prerequisites

- Java 21
- Maven 3.9+
- k6 for the load tests
- Docker only when building a container image
- An OBaaS environment with Oracle Autonomous Database and SigNoz for the full deployment walkthrough. Start with Oracle's [OBaaS setup guide](https://oracle.github.io/microservices-backend/obaas/docs/setup/) to install or access an environment.

## Build and run locally

Build the project from the repository root:

```bash
mvn clean package
```

Run the service:

```bash
java -jar helidon-credit-service/target/helidon-credit-service.jar
```

Without an OBaaS-injected datasource, the service uses an embedded H2 database in Oracle compatibility mode. That lets attendees run both request paths locally; the full Oracle and SigNoz walkthrough requires OBaaS.

Verify the service:

```bash
curl -s http://localhost:8080/health/simple | jq
curl -s -X POST http://localhost:8080/credit-decisions/evaluate \
-H 'content-type: application/json' \
-d @api/sample-requests/approved.json | jq
```

## Service API

```text
POST /credit-decisions Evaluate and persist a decision when Oracle is configured
POST /credit-decisions/evaluate Evaluate without persistence
GET /credit-decisions/{id} Fetch one decision
GET /credit-decisions/customer/{id}
GET /health/simple
```

The shared contract is [api/openapi.yaml](api/openapi.yaml).

## Reproduce Demo 3: virtual-thread sweet spot

This scenario removes the database from the request path while retaining the 65 ms simulated blocking workflow:

```bash
k6 run \
-e BASE_URL=http://localhost:8080 \
-e VUS=250 \
-e SLEEP=0 \
-e DURATION=300s \
load-tests/credit-decision-evaluate.js
```

Expected signals:

- about 250 active virtual threads during the load window;
- no pinned virtual threads or submit failures;
- successful HTTP checks and a stable request rate.

## Reproduce Demo 4: database-backed request work

Run this against an OBaaS deployment with Oracle configured:

```bash
k6 run \
-e BASE_URL=http://localhost:8080 \
-e VUS=250 \
-e SLEEP=0 \
-e DURATION=300s \
load-tests/credit-decision.js
```

The DB-backed path performs the same simulated waits as Demo 3, then writes a decision through Helidon Data, Jakarta Persistence, and Oracle JDBC. It should complete fewer iterations than the no-database path because each request now includes database and transaction work.

Compare the k6 summaries using the same target, VUs, duration, and client pacing. In the presentation run, the no-database scenario completed 590,701 requests at 1,968 requests/s; the DB-backed scenario completed 405,411 requests at 1,351 requests/s, both with zero HTTP failures.

## Inspect the results in SigNoz

After each scenario, use the same time window in the following dashboards. The goal is to connect the k6 client results to the Java runtime and, for Demo 4, to the database.

### Helidon JVM Details

- **Requests Per Second:** confirm the sustained server-side rate and compare the two runs.
- **Helidon Virtual Threads:** during both 250-VU runs, active virtual threads should be close to the offered load; pinned virtual threads and submit failures should remain at zero.
- **CPU and Memory Usage:** use these as context for the load rather than treating them as the sole explanation for a throughput change.

### Service and trace views

- **Helidon MP Details** or the service overview: inspect request rate, latency percentiles, and error rate.
- **Traces:** open a `POST /credit-decisions` trace from Demo 4. It should show the Oracle database work beneath the request span.
- **Logs:** move from that trace to the correlated application log line when explaining what the service did.

### Oracle Database Details

- **User commits** and **execute counts:** the DB-backed run should make these rise; the presentation run showed roughly one user commit per successful create request.
- **Active sessions** and **system wait classes:** use these to see whether database work is active or visibly constrained.
- **Top SQL:** distinguish application SQL from database monitoring and housekeeping queries before drawing conclusions.

For the two scenarios, expect active virtual threads to remain close to the requested 250-user load while the DB-backed path has a lower request rate and higher latency. In the presentation run, the no-database scenario completed 590,701 requests at 1,968 requests/s; the DB-backed scenario completed 405,411 requests at 1,351 requests/s, both with zero HTTP failures.

The result is not a claim that virtual threads make database work faster. They make Java waiting cheaper. Persistence still adds JDBC, network, SQL, and transaction-completion cost to each request.

## Deploy to OBaaS

Use [deploy/obaas/README.md](deploy/obaas/README.md) to build the image, deploy the Helm chart, expose the service through APISIX, and locate the SigNoz credentials in the cluster.
Loading