Static data in module

While creating a reusable module that will be used in many projects a wanted to include 'static' or default data like SQLQueries (executed via Java) but stored in an entities and thus editable in management forms. Is there a way to save static data? Or should I include a microflow that creates the objects once after importing the module and running the app for the first time?
1 answers

I usually mimic static data by creating a microflow that receives the first object of a certain entitytype, or that creates one instance (with the default values) if none existed yet.