Lightweight Architecture

Clean, understandable communication. No bloated frameworks or complex toolchains.

Simplicity by Design

Oorian uses straightforward JSON messaging. No magic, no complexity.

Minimal Client

No heavy client-side framework. Just a small JavaScript library for DOM updates.

JSON Messaging

All communication uses simple JSON. Easy to understand, debug, and extend.

No Build Tools

No webpack, no npm, no node_modules. Just compile your Java and deploy.

Fast Startup

Lightweight means fast. No heavy framework initialization on page load.

Easy Debugging

See exactly what's sent and received. JSON is human-readable in dev tools.

Zero Dependencies

No external Java libraries. Just standard J2EE/Jakarta APIs. No version conflicts or dependency hell.

JSON Message Protocol

Oorian uses a simple, documented JSON protocol for all communication.

Event Message (Browser → Server)

json

{
  "type": "event",
  "event": "click",
  "sourceId": "save-button",
  "data": {
    "clientX": 245,
    "clientY": 180,
    "button": 0
  }
}

Update Message (Server → Browser)

json

{
  "type": "update",
  "updates": [
    {
      "id": "status-label",
      "action": "setText",
      "value": "Saved successfully!"
    },
    {
      "id": "save-button",
      "action": "setDisabled",
      "value": true
    }
  ]
}

No Build Tool Complexity

Modern frontend development often requires complex toolchains. Oorian keeps it simple.

Typical Frontend Stack

Node.js and npm
Webpack or Vite or Parcel
Babel for transpilation
package.json with 100+ dependencies
Build scripts that break mysteriously
Hours debugging build issues

Oorian Stack

Java compiler (javac)
Standard WAR deployment
That's it

Performance Benefits

Fast Initial Load

No massive JavaScript bundle to download and parse. The Oorian client library is small and fast.

Efficient Updates

Only changed elements are updated. The server sends minimal JSON diffs, not entire page re-renders.

Server-Side Efficiency

Java is fast. Your business logic runs on efficient server hardware, not in a browser sandbox.

Network Efficiency

JSON messages are compact. No bloated protocol overhead or unnecessary data transfer.

Memory Efficiency

No client-side virtual DOM or framework state. Browser memory usage stays low.