What is LingFrame?
LingFrame is an open-source (Apache-2.0) in-process runtime governance framework for the JVM, built for JVM applications that must run for a long time yet keep changing in parts. With independent business JARs (Lings) as the boundary, it closes the loop of module load/unload, multi-version canary, call governance and observable reclamation inside a single JVM.
How does LingFrame relate to microservices and K8s? Is it a replacement?
No, it is not a replacement. The two work together, and you don’t have to pick one. K8s, gateways and service meshes manage what lies between processes: deployment scheduling, network routing, capacity scaling and instance-level rolling updates. LingFrame manages what lies inside the process: module load/unload, weighted canary, call governance, lifecycle and reclamation observation. LingFrame does not handle cross-process network communication, cluster scheduling or node disaster recovery.
What are a Ling and LingCore?
A Ling is a business JAR that can be loaded, run, governed and unloaded independently. It isolates private dependencies with its own ClassLoader and talks to its host through explicit contracts. LingCore is the host application that carries Lings.
Which JDK and Spring Boot versions does LingFrame support?
The default environment is Spring Boot 2.7 with JDK 8, and Spring Boot 3.5 with JDK 17 is also supported. Maven is required to build. A Ling can be a Spring Boot business module, or a Native Java module that does not start a Spring container.
What is the fastest way to try LingFrame?
The fastest way is to run the official example: clone the repository, build and start the example LingCore, then open http://localhost:8888/dashboard.html to watch Ling loading and routing. You can also open the live demo dashboard at dashboard.lingframe.cn first (public demo token: lingframe) to get familiar with the operations; before adopting, you still need to verify your own business locally.
How much overhead does LingFrame add?
July 9 empty-business JMH averages: governance only ≈0.8 µs; with terminal invocation ≈19 µs. Not p95 or v0.4.7 results; test your workload.
Can it be used in production now?
v0.4.7 is still Pre-1.0. Validate real business workloads, dependencies and resource release in a test environment first, then check authentication, configuration and observability against the production hardening checklist.
Can the Shared API be hot-updated together with a Ling?
No. Contracts already loaded into the shared boundary do not support hot update or hot unload, in order to keep types consistent across ClassLoaders. You can preload a new contract package; breaking changes to existing contracts still require a process restart.
Does a finished unload mean memory drops immediately?
No. The unload flow stops routing, drains requests, closes the context and releases references; actual reclamation of the ClassLoader and class metadata also depends on leftover references and the JVM GC. Verify with observation rather than the unload status alone.
Are all JDBC calls covered by data source governance?
No. Managed data source governance mainly covers the DataSource injected through Spring; raw JDBC connections created by hand are not within the same interception boundary. Verify resource ownership and transaction propagation against the documentation.
Is the Dashboard required?
No. The Dashboard is an optional module that must be enabled explicitly. You can also manage things through configuration or Actuator. When authentication is enabled in production, configure a dedicated access token instead of reusing the public demo token.