Instead of storing data to an SQL database, we want to work with NoSQL databases and preferrably combinations of all such things.
Data storage is a diverse landscape of technologies. Triple stores, graph databases, persistent event streaming are but a few technologies that have become commonplace. We want Ampersand to link up with such technologies to serve a wider spectrum of problems.
Ampersand is prepared for this by the plug-mechanism.
To document our long-term vision, this page summarizes the plans we have with Ampersand.
This chapter discusses future plans. Click on the hyperlinks for details
In this video discusses the plans in 7min30 (in Dutch)
To understand our plans, this section describes the current state of Ampersand.
Instead of storing data to an SQL database only, we want to other types of databases to work with Ampersand as well. Especially NoSQL databases (e.g. triple stores, graph databases, persistent event streaming) seem very suited for Ampersand.
To generate APIs is what Ampersand does already. We also want to generate documentation of the (generated) API to make it more useful in real life.
To work closer in sync with the semantic web we want to accept OWL and RDFS input. Currently Ampersand accepts Ampersand-syntax, Archimate-xml, and Excel as input.
To generate reactive web-applications instead of a classical object-oriented web-application is why we want to refactor the Ampersand front-end.
To generate reactive web-applications instead of a classical object-oriented web-application is why we want to refactor the Ampersand front-end.
To work closer in sync with the semantic web we want to accept OWL and RDFS input.
To understand future developments, you may want to know where we stand now.
One purpose of Ampersand is to generate a web-application. Currently, the generator and the generated application follow this architecture:
The architecture is explained in more detail in this chapter.
