Deployment options

[Jamstew2]

Related to the issue documented here: #17 (comment) we understand that adopters of our code may wish to pursue a different deployment path / options. Here are the choices we anticipate being available, these would need to be enabled through further development enhancements to the existing code:

• Choice of object storage (for example Amazon S3 or Azure Blob)
• Alternative to object storage such as an on premise block storage array
• Choice of databases which could be another noSQL DB (e.g. Mongo) or other DB options such as Db2, MySQL, SQL Server etc.

Options for the deployment of the Node.JS API and React website:

• At present to tutorial explains how to deploy locally and on IBM Cloud via Cloud Foundry
• It is possible to re-package the code to run in other environments such as container platforms (Redhat Openshift or alternative Kubernetes / container services) or using other cloud services capable of running a Node.JS / React application.

[upkarlidder]

@Jamstew2 : really good points. Capturing my thoughts here as well.

• Node.js API and React website - we can add Dockerfiles and deployment configurations so these can be containerized and then deployed to K8s infrastructure of choice. This could be a progression from run local -> run local in container -> deploy to K8s
• for services like databases and COS, the API acts like an abstraction layer already. We can move to open source container versions of these services as you suggested.
  • minIO for S3 compatible open source COS
  • CouchDB for open source document based DB. Cloudant is based on CouchDB

[github-actions]

👋 Hi! This issue has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed.