What is Graph-Oriented Programming (GOP)?
If you search the Internet, you will find some articles putting various meaning under the “Graph-Oriented Programming” terminology, and none of them can really be considered as a “programming paradigm”, in the usual acceptation of this term.
For GraphApps, here is a definition of the graph-oriented programming paradigm:
Graph-Oriented Programming is a new programming paradigm that defines a graph-oriented way to build software. The Graph-Oriented softwares built with this programming paradigm use (directed attributed) graph databases on the backend side.
This programming paradigm is cumulating the benefits of several other programming paradigms: object-orientation, functional programming, design by contract, rule-based programming. However, it is consistent in itself and do not need to be aware of any other programming paradigms.
This programming paradigm enables to develop long lasting business applications that do not generate technical debt. It provides a different answer to the maintenance and evolutions issues, especially for applications that must manage evolving regulations or a high number of business rules. Applications can evolve structurally without having to retest everything and migrate the data.
What Do GraphApps Provide?
GraphApps provides the first worldwide designer (GraphApps Designer) and web framework (GraphApps Web Framework) to push for and implement graph-oriented programming.
Our web framework is developed in Java and is available for Neo4j and OrientDB databases.
What’s in this section?
In this section, we explain what is graph-oriented programming and why GraphApps brings a revolutionary design and programming paradigm to software engineering.
In the coming weeks, new pages will be added in this section.
- Episode 1: Genesis of GraphApps
- Episode 2: Coupling in Enterprise Applications
- Episode 3: coming soon: Manipulating Graphs of Business Objects (and Business Relationships)
- About Graph Databases