InterSystems IRIS is a Complete Data Platform
InterSystems IRIS gives you everything you need to capture, share, understand, and act upon your organization’s most valuable asset – your data.
As a complete platform, InterSystems IRIS eliminates the need to integrate multiple development technologies. Applications require less code, fewer system resources, and less maintenance.
For standalone installations I always recommended to use custom namespaces and not the USER namespace.
However, what about Docker?
In many Dockerfiles I see the creation of additional namespace, but why, if only one namespace is required?
What do you think?
We found out recently that when compiling an objectscript class that has a java projection, using the -d flag, it ignores it for the projection part:
.png)
After talking with intersystems luckily the've provided a solution that will be included in the next release:
.png)
Hello All,
I have been using IRIS / Ensemble for over a decade and appreciate lot of it's functionalities and features, however besides having a UI of 80's era (which doesn't bother me), what I believe where IRIS is lacking is lack of out of the box connectors (services/operations).
If we look at IRIS's competitors for eg Mulesoft, Talend, Boomi they all have hundreds of pre-built connectors for major applications like Salesforce, SAP etc and cloud services like Azure, AWS etc to store and retrieve information and data.
Just to give an idea here is a link of Dell Boomi connectors
Hello everyone,
As someone who is new to the world of InterSystems technology, I have been looking for the best resources to learn more about it.
I have heard great things about InterSystems technology, particularly its speed and scalability, and I want to make sure I have a solid understanding of it before diving in further. From what I understand, the official InterSystems courses cover a wide range of topics and are taught by experts in the field.
I would appreciate any recommendations on which courses to take, particularly if there are any that provide a good foundation for beginners.
Hi guys!
Suppose you developed a tool, framework, library on InterSystems ObjectScript for InterSystems Data Platform, share it via Open Exchange and want people to install it.
What is the best strategy if it is a library and supposed to be called from different namespaces?
Here are the following thoughts:
1. Tool's developer should be able to use globals to read/store data the tool needs.
2. Tool's consumer should be confident, that the thing he/she installs will not harm the application's data.
3. A tool should be callable from any application's namespace.
4. Tool's installation(in general) should not request manual security changes (e.g. grant the write access to IRISLIB) and %YourClass is not an option.
5. It's easy to uninstall the tool - just delete the namespace/database (maybe delete some web-apps too).