...
Overall architecture
FOLIO is made of microservices micro services that communicate through an API gateway. It relies on HTTP messaging between modules to get things done.
...
Stripes: In production environment, near to medium term, will be dealing with static bundles. Can be prepackaged in a hierarchy by FOLIO – platform core circ + inventory and platform core+ everything else. Can build own platform but there are a lot of interdependencies inter-dependencies in the core of the UI with password validator and inventory storage. Some apps make sense to work on their own.
...
In production need to run Okapi in clustered mode with shared storage – supports Postgres theoretically it still supports mongo MongoDB but won’t be recommended.
...
Temporary fix is to pin Hazelcast version into Okapi. Only a problem if Hazelcast upgrades. ? Jason says he sees inconsistencies. No data loss, just loss of commuinicationcommunication. Okapi persistence doesn’t change very much.
...
Do you use Okapi to deploy your system. O Okapi uses docker API to deploy which is fine– fine – but if you are running Okapi in a pseudo-stateless way in a container – that’s where Kubernetes comes in.
...
Don’t want to use Okapi as orchestration tool (Jason). Does the project offer any tooling as part of the project? There will be mutiple multiple steps. Jason’s ok with O Okapi triggering data migration but if it hoses my database that is a problem.
...
Could run separate DB for each module. Limitation that can run each tenant with own dtabase database – architectural limitation of RMB. Separate backend is needed – there is issue for that in FOLIO.
Change to run multiple database – but need to scale postgres connections – can’t pull connections from separate database – explode the need for connections. That deicision decision needs to lie on devops side. Configuration limitation now. Can’t run multiple databases using the same back end. What’s the better way. Running different copies of same module is a computer cost.
...