Tally+
Technology / Architecture

Tally+ ecosystem architecture

How we design the Tally+ platform: architecture principles and a reference target architecture for modular services, integrations, and channels.

Architecture principles

Tally+ ecosystem — architecture principles

architecture

Well-architected

  • As a foundation for all design adhere to well-architected principles (reliability, security, cost optimization, operational excellence, performance efficiency).
view_module

Modular

  • Build toward modular components.
  • Low coupling and strong cohesion results in stable platforms.
  • Reusable within the platform, and potentially across platforms.
  • Increase flexibility within a module.
  • Increase flexibility between modules.
integration_instructions

Integration enabled

  • Follow industry standard enterprise integration patterns for both internal integrations between modules and external integrations.
  • Enable functionality through APIs for internal and potentially external use.
  • Use events to notify components of changes and potentially expose them externally through webhooks.
verified_user

Compliant

  • Any solution must be compliant for the domain in which it operates.
group_work

Consolidated

  • Consolidate common functionality in modules.
  • Reduce compliance risks.
trending_up

Incremental evolution

  • Prioritise incremental evolution to big-bang cutovers.
  • Apply standard migration patterns when enhancing software (for example strangler fig, branch by abstraction, and parallel run).
  • Deliver value early.
  • Minimise risk.
stars

Value-driven priorities

  • Key-value streams (for example billing, payments, market).
  • Areas of competitive advantage.
  • Innovation and growth.
  • Compliance.
  • Security.
Target architecture

Tally+ ecosystem — target architecture

Tally+ is modular-by-design and can be fully integrated with a retailer’s enterprise ecosystem, providing integrations for strategic platforms.

Tally+ EOS reference architecture diagram: retailers, portals, core operating functions, ISO / RTO market interfaces, and payment agency flows.

Reference diagram — illustrative partners and systems; regional deployments vary.

Inside the Tally+ core platform

Unified access and experience layers sit above the modular service stack; integration and events support connectivity.

  • Unauthenticated: website, social, sales portal.
  • Authenticated: customer portal, customer app, business portal, agency portal.
  • Integration (generic and custom) and events for module-to-module and enterprise connectivity.

Enterprise context (reference)

Typical client-side system integrations:

  • Enterprise data platform
  • Marketing; ERP for people and finance
  • Customer’s in-place supporting systems

Native integrations (reference categories)

Examples shown on the target diagram — swap for your market and compliance footprint.

Market

ERCOT, PJM, NYISO, SMT

Payments

Authorize .Net

Mail, comms and notifications

Twilio, SendGrid, MsgMe

Credit Check

Credit Check, Equifax, TransUnion