Layer-Crossing Call Violations

A standard layered or clean architecture organizes application logic sequentially. Method calls should flow down in a structured hierarchy (e.g., Controllers call UseCases/Services, and UseCases/Services call Repositories). Skipping layers (such as letting UI/Web Controllers invoke low-level Database Repositories directly) creates bypassing shortcuts that bypass core validation rules, transactional envelopes, and business logic.

[Web Controller] ---> [Business Service] ---> [Repository]
       |                                             ^
       +----------- PROHIBITED DIRECT CALL ----------+

---

💡 The Rationale

• Consistency of Business Flow: Bypassing services risks running queries without essential validations, audit logging, authorization filters, or cache updates.
• Transactional Integrity: Databases usually expect transactional scopes (like @Transactional) to reside on your service-layer boundaries. Calling repositories directly from HTTP controller runtimes can result in database read anomalies, stale reads, or loose connections.
• Refactoring Simplicity: Maintaining a strict sequential chain guarantees that you can change the underlying repository implementation safely by modifying only the intermediate service layer.

---

🛠️ Implementation with Konture

You can detect skipped boundaries by setting up package import and class dependency blocks on your structural groups using the classes() DSL.

1. Banning Direct Repository Calls from Controllers

You can assert that any class ending with Controller or residing in the presentation layer must not reference classes inside your data/repository layer:

import io.github.baole.konture.*
import org.junit.jupiter.api.Test

class LayerCrossingTest {

    @Test
    fun `controllers must not bypass services to access repositories directly`() {
        Konture.classes {
            that().resideInAPackage("..presentation..")
                .should().notDependOnClassesInAnyPackage("..data.repository..")
        }
    }
}

2. Ensuring Repositories are Only Accessed by Authorized Layers

Conversely, you can assert that your Repository components are strictly only dependend on (or imported by) classes inside the Service or Domain package boundary:

import io.github.baole.konture.*
import org.junit.jupiter.api.Test

class RepositoryAccessControlTest {

    @Test
    fun `repositories must only be accessed by intermediate services`() {
        Konture.classes {
            that().resideInAPackage("..data.repository..")
                .should().onlyBeAccessedByAnyPackage(
                    "..data.repository..", // Self-access
                    "..service..",        // Intermediate services
                    "..di.."              // DI wiring modules
                )
        }
    }
}

---

🚨 Example Failure Output

If a controller ProductController bypasses validation and invokes ProductRepository directly:

AssertionError: Architecture violation: Controllers must not bypass services to access repositories directly
Class 'io.github.baole.konture.sample.presentation.ProductController' has forbidden dependency on 'io.github.baole.konture.sample.data.repository.ProductRepository'
  (at /path/to/project/showcases/sample-gradle/presentation/src/main/kotlin/io/github.baole.konture/sample/presentation/ProductController.kt:8)

The error prints the exact line containing the bypassed import statement, allowing you to instantly correct the leak.