REST interface is good, but could we add business valdation before mutating data? Because bulk of the work backend does is this business logic. How could we do this?
The short answer is yes. Macrometa integrates a function as service (FaaS) which can be hooked into the database and be triggered by events on a stream or a data collection.
So you can for example do the following:
Expose a RESTful or GraphAPI (included deep nested queries in graphQL) for one or more collections - when mutating, attach a validation function to the collection as a trigger that is called before the mutation is applied to the DB. You can also have a trigger that calls a function after the mutation is complete.
One can also do this on streams with functions being triggered to a specific topic.
Lastly - there is full support for running containers as well and you can use the endpoints exposed by the container as a trigger.
Oh and one more thing - the dB is real time. It will notify clients of updates to collections automatically (like firebase).
Shares some feature overlap with dynamodb (key/value and document dB interfaces). Where we differentiate - global replications across all our 25 global POPs (50 by end of 2019). Integrated graphQL generator (rest as well), real-time: dB will notify clients of changes to data I.e. no need to poll, rightly integrated with streams and pub/sub, run functions and containers as triggers or stored procedures to the DB, geo query: query by lat/long/height, elastic search integrated (July 2019). There’s more - will announce in April
