I want to start this project and wants to know the best practices, you guys using to arrange the project. I have done lot of mvc projects and API's in c#. But Intersystems is new to me. Please give me some suggestions like how can I Arrange the objects. Like for eg. Where can I store the productions objects like services,process and operations. will that be like under each resouces folder name? and what are the base classes, and how can I store them? basically please give me some idea about how Can I arrange them .
We are currently implementing the Data Innovations Instrument Manager product. In setting up our backup process we are wanting to use Veam snapshots. The application runs in a Caché 2016.1/Windows Server 2016 instance. We are running an HA primary/secondary/arbiter config. The statement below is from DI. I am curious to see what others that have implemented the DI Instrument Manager in the same or similar config have in place for backup.
"DI recommends is recommending that we not perform snapshots, but if you do choose to do so, here is some important information to consider.
I've been working on deploying an IRIS for Health environment in EKS. There is a video session in the InterSystems learning portal about this feature but I have not succeeded in finding the proper documentation and resources to use this in my Kubernetes cluster.
Has this been deprecated/discontinued? Any idea where can I find the resources? Should I stick to StatefulSets instead of using the IrisCluster resource type provided by this operator?
Our organization is looking to expand our Coding Standards to be more in alignment with best practices.
I was wondering if the there are developers here that would not mind sharing any existing documents. Our scope would be this document be applicable to new hires learning Cache all the way up the chain.
I'm almost running out of disk space so I want to move 1 DB to a different hard drive. It's a rather simple but lengthy action during a shutdown of IRIS. But is this somehow possible under runtime in a stand-alone installation? I'm looking for kind of a "local drive failover"
We have a need to track Database changes over time - down to the SQL level of granularity if possible. Such as: User xyz runs routine ^abc and we get something similar to a changelog that tells us: table A had this value updated, insert, update etc....
Is that possible using IRIS level tools (Audit Log, Journal File, etc...) , is there a way to convert the global sets and kills from the journals into SQL level changes?
After running an extensive block of daily statistics my IRISTEMP has expanded dramatically. But FreeSpace shows 97% unused and FREE space. How can I shrink IRISTEMP in runtime without shutdown and manual intervention (which was the traditional approach)
I am looking to migrate a few legacy debt collection applications built using InterSystems Cache to AWS. Does anyone here have any experience, ideas and best practices on migrating Cache products to the public cloud?