JPA
- JPA
- Jakarta Persistence API
A JVM object-persistence specification; Hibernate is one implementation. A persistence context tracks entities, but flush timing, transactions and SQL still matter.
KNOWLEDGE AT HAND
551 concepts from programming, backend development and GitOps. Definitions, acronym expansions and references — no account required.
Results: 551
A JVM object-persistence specification; Hibernate is one implementation. A persistence context tracks entities, but flush timing, transactions and SQL still matter.
Java execution environment. Our exercises/build need a full JDK with javac rather than only a runtime.
Source documentation ↗An interactive Java console for small expressions and experiments. Console results help explain a mechanism but do not replace application tests.
Source documentation ↗A text data format with objects, arrays, numbers, strings, booleans and null. Valid JSON syntax does not establish schema or business-rule correctness.
A collection of JSON Web Keys, often published by an issuer for JWT signature verification. Validate the trusted issuer, algorithm and rotation; downloading a key alone does not authenticate a user.
Source documentation ↗A JVM test framework with annotations and assertions. It checks executed cases; a reference test does not complete a learner attempt.
Source documentation ↗Compilation during program execution, often based on runtime profiling. Warmup and optimization affect benchmarks.
Source documentation ↗A virtual machine executing Java and Kotlin bytecode, among others. Sharing a runtime does not make the languages’ semantics identical.
A token format containing claims such as issuer, audience and expiry. Signature checking is only part of validation; a typical signed JWT does not hide its contents.
A product name or identifier; no acronym expansion is invented.
The name of a Kotlin compiler generation. Verify compatibility on the pinned version and plugins, not merely the compiler name.
Source documentation ↗An event-streaming platform with partitions and consumer offsets. Ordering has a defined scope, and external database effects still need retry handling.
A tool running a local Kubernetes cluster with nodes in containers. Useful for labs and tests. It is neither a Docker engine nor a production cluster; a project defines compatible node images and tool versions.
Source documentation ↗Choose a solution whose input, rule and result are easy to trace. Fewer characters do not justify unreadability or missing error handling.
A statically typed language used here for JVM comparison. Null safety, read-only collections and coroutines have limits; they do not automatically ensure correct Java integration.
A Java-library type whose nullability is not fully known to Kotlin. Access can fail for null; validate at the boundary and use an explicit type. !! alone is not domain validation.
Source documentation ↗Node agent supervising assigned Pods and reporting their state. It does not replace the Deployment controller or cluster scheduler.
Source documentation ↗A platform running containerized applications and reconciling their state. Controllers work toward declared desired state; a working cluster does not automatically mean a correct application.
Source documentation ↗A loop observing state, comparing it with a declaration and attempting to reduce the difference. The whole process is not atomic; failures and further reconciliation are part of the model.
Source documentation ↗A controller declaratively managing application Pod replicas and updates. A successful rollout does not yet prove business correctness.
A controller encoding operational knowledge, often for a custom resource. Its permissions and behavior belong in failure and recovery design.
Source documentation ↗Kubernetes’ basic execution unit, containing one or more collaborating containers. Pods can be replaced; their names should not be durable business-data identities.
A stable way to access a selected set of endpoints, usually Pods. A Service’s existence does not mean the application is ready or externally exposed.
Composes and modifies manifests through bases and overlays. Describes environment differences without erasing semantic differences between providers.
Source documentation ↗A compact function expression passed as a value, such as a list transformation. It may capture surrounding state; concise syntax does not imply absence of side effects.
PHP/Laravel static analysis built on PHPStan. It detects selected typing and usage problems; tests still verify runtime effects.
Source documentation ↗A PHP framework offering web-application conventions and tools. Its container, routing and Eloquent help development, but domain rules and transaction boundaries still require design.
A Laravel library for AI features inside an application. Unlike Boost it implements product behavior and requires data boundaries, cost/failure controls and quality tests.
Source documentation ↗Laravel agent-assisted development support: context, guidelines, documentation and MCP tools. It is not application AI functionality. Agent permissions remain a separate decision.
Source documentation ↗Laravel request serving that keeps the application alive in workers. It reduces repeated bootstrap but requires control of customer state, memory and dependency lifecycle.
A PHP style formatter for Laravel projects. Consistent diffs aid review but do not prove rule correctness.
Source documentation ↗