No More Pod Restarts for Config Changes

True Real-Time Config Management! Anything you change in your dashboard online - instantly affects your application - With Zero Latency! Why Zero Latency? How is it True Real-Time? Because It's a WebSocket based SDK and Web Admin! The SDK always have the latest data locally - in memory. You can freely call the SDK getters/setters at no cost! even inside algorithm loops! it's all local variables! Lite Rock - Less Talk - Feel the magic yourself: We've prepared these user & pass for you: Username: dev-to-design Password: cixF5v.c`5NegGp3YKyt5v So you can Login to your free Kiponos ride and start exploring the service right away! How does the SDK work in your application? It's a Java SDK on Maven Repository So you can simply include it's name in your build. (For example, the current one is: io.kiponos:sdk-boot-3:4.4.0.250319) Usage Example in your application: // Get these from the account - click [Config SDK] on the side bar. // // SET KIPONOS_ID="Jk7RA" // SET KIPONOS_ACCESS="2HqCQ" // // Each Config instance has a unique path identified by VM param: // -Dkiponos="['Try-Me']['1.0']['Dev']['Base']" // // public class MyAwesomeApplication { static Kiponos cfg = Kiponos.createForCurrentTeam(); public static void main(String... args) { int maxPageSize = cfg.getInt("my-max-page-size"); String dbHost = cfg.folder("DBs","postgresql").get("host"); } } Once that set you can forget about any config files forever! No More Yaml files, No More application.properties, No More Redeploys, No More Restarts, No More Reload or Fetch for any config updates! Your SDK has the latest config data - always! Since WebSockets are used to dispatch delta changes only, your SDK get's "pushed" with updates in real-time as they happen by any member of your team, on your runtime environment. You get Role Per Team Based Access Control We support users as members of multiple teams so config updates are permitted by roles per relevant team. For example: A Developer User can modify staging-team configs, but can read only qa-team configs. This architecture natively supports true real-time, zero latency: Feature Toggles. Validations. SQL statements AI Training parameters! I18N and L10N (No more redeploying those translations!) Log Levels Make Coffee? - Yes! - Run the SDK in your coffee machine - and you control your coffee machine remotely - in real-time. You name it! What else developers, testers, automation, devops need? This architecture is essentially so powerful, it's in fact equivalent to modifying your running application's hard coded variables - in real-time - while running in production, or in the middle of a CI/CD pipeline, or in the middle of heavy calculations - all without modifying your code! without any costs on I/O for the change. And all - from a remote beautiful online admin page. Enjoy this revolution! Respectfully yours, Kiponos.io

Apr 21, 2025 - 19:32

True Real-Time Config Management!

Anything you change in your dashboard online - instantly affects your application - With Zero Latency!

Why Zero Latency? How is it True Real-Time?

Because It's a WebSocket based SDK and Web Admin!

The SDK always have the latest data locally - in memory. You can freely call the SDK getters/setters at no cost! even inside algorithm loops! it's all local variables!

Lite Rock - Less Talk - Feel the magic yourself:

We've prepared these user & pass for you:

Username:

dev-to-design

Password:

cixF5v.c`5NegGp3YKyt5v

So you can Login to your free Kiponos ride and start exploring the service right away!

How does the SDK work in your application?

It's a Java SDK on Maven Repository

So you can simply include it's name in your build.
(For example, the current one is: io.kiponos:sdk-boot-3:4.4.0.250319)

Usage Example in your application:


// Get these from the account - click [Config SDK] on the side bar.
// 
// SET KIPONOS_ID="*********Jk7RA"
// SET KIPONOS_ACCESS="*********2HqCQ"
//
// Each Config instance has a unique path identified by VM param:
// -Dkiponos="['Try-Me']['1.0']['Dev']['Base']"
// 
// 
public class MyAwesomeApplication {
  static Kiponos cfg = Kiponos.createForCurrentTeam();

  public static void main(String... args) {
    int maxPageSize = cfg.getInt("my-max-page-size");
    String dbHost = cfg.folder("DBs","postgresql").get("host");
  }

}

Once that set you can forget about any config files forever!

No More Yaml files,
No More application.properties,
No More Redeploys,
No More Restarts,
No More Reload or Fetch for any config updates!

Your SDK has the latest config data - always!

Since WebSockets are used to dispatch delta changes only, your SDK get's "pushed" with updates in real-time as they happen by any member of your team, on your runtime environment.

You get Role Per Team Based Access Control

We support users as members of multiple teams so config updates are permitted by roles per relevant team.

For example: A Developer User can modify staging-team configs, but can read only qa-team configs.

This architecture natively supports true real-time, zero latency:

Feature Toggles.
Validations.
SQL statements
AI Training parameters!
I18N and L10N (No more redeploying those translations!)
Log Levels
Make Coffee? - Yes! - Run the SDK in your coffee machine - and you control your coffee machine remotely - in real-time.
You name it!

What else developers, testers, automation, devops need?

This architecture is essentially so powerful, it's in fact equivalent to modifying your running application's hard coded variables - in real-time - while running in production, or in the middle of a CI/CD pipeline, or in the middle of heavy calculations - all without modifying your code! without any costs on I/O for the change.

And all - from a remote beautiful online admin page.

Enjoy this revolution!

Respectfully yours,
Kiponos.io