saveourtool/save-cloud

Backend: JPA / spring-data / hibernate improvements

Open

#575 opened on Feb 15, 2022

View on GitHub
 (1 comment) (0 reactions) (2 assignees)Kotlin (4 forks)github user discovery
enhancementgood first issue

Repository metrics

Stars
 (38 stars)
PR merge metrics
 (PR metrics pending)

Description

Mark entities / columns / transactions:

  • readonly (@Transactional(readOnly = true)): reduces memory consumption
  • non-nullable as per DB constrains (@Column(nullable = false)) => properties can have non-nullable type
  • Make all associations lazy
  • others?

Hibernate L2 caches:

Some entities that are worth caching:

  • Users, user-project associations (#580, #649) - won't change often, but are required for all permission checks
  • Projects, organizations - won't change often, but are often required by frontend

build time enhancement

Contributor guide

Research direction
Implement the listed improvements: mark transactions as readOnly, add nullable=false constraints, make associations lazy, and consider enabling second level cache with Hibernate.
Tech stack
kotlinspring
Domain
backend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
KotlinSpringHibernate
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50