com.viaoa.overview.html Maven / Gradle / Ivy
Show all versions of oa-core Show documentation
Object Automation (OA) by Via Object Architects (ViaOA, Inc.)
"All programs are made up of objects and collections of objects."
OA automates how they work together.
At the core of OA is the object model that is an object-relational, observable, reactive, functional, distributed object graph.
This graph of objects and collections automatically work with persistence layers, frameworks, UI, reporting, microservices, and more.
Objects are kept in-sync across servers, so that a change on one computer is automatically changed on all other computers.
Since the objects are observable, systems can listen for specific changes and react. Formulas can be recalculated, UI's updated,
processing, filtered data updated, security enforced, etc.
The Model Driven approach defines the entities, relationships, persistence, business logic, security, UI, endpoint access, work-flow and more.
Full software systems can be visually designed and then automatically generated using the OA library, OABuilder visual modeling tool, along with code generation and templates.
See www.viaoa.com for more information.
Key Concepts for automation
- observable objects and collections - core for allowing reactive object graphs
- property paths - dot separated paths for interacting with object graphs
- remoting/distributed - allows scaling and failover, where everything works like a single application.
- datasource independent, ORM, XML, JSON, yaml, REST, ... - any data, anywhere
- desktop UI - automated rich components - rich UI and reporting
- web UI - componenized web apps.
- reflective - techniques for automating interactions using object graphs, components and code.
- metadata - object data, discovery, and includes business rules, security, callbacks, so that the model is the core.
- functional - realtime filtering, merging, object graph, visiting, joins, groups, more.