InterSystems ObjectScript is a scripting language to operate with data using any data model of InterSystems Data Platform (Objects, Relational, Key-Value, Document, Globals) and to develop business logic for serverside applications on InterSystems Data Platform.
Hi everyone!
My name is Nikita Mikhailov, and I am a backend engineer with 4 years of experience specializing in InterSystems IRIS, ObjectScript, MUMPS, and .NET. I thrive on untangling legacy codebases, solving complex concurrency or performance bottlenecks, and building clean, modern APIs.
Key Highlights from my work:
Performance Optimization: Slashed average API response times by 90% (from >1s down to ~100ms) by implementing custom caching layers and background processing.
Hi everyone,
I am testing an OAuth2 setup on InterSystems IRIS 2026.1 (Community Edition), based on a workshop with separate Auth Server and Resource Server instances (https://community.intersystems.com/post/learn-how-use-oauth2-openid-con…).
On the Resource Server, when I try to use Dynamic Registration and Save in OAuth 2.0 Client Configuration, I get this error:
ERROR #8881: Dynamic client registration endpoint is not configured.
What I already checked:
On save the ClassMethod:
ClassMethod create() [ Language = python ] {
print("python")
}
it has received the error :
Hi folks!
Our community is growing rapidly, and the knowledge base is incredibly vast. Whether you're a newbie, confused, and unsure where to start, or a seasoned IRIS veteran who occasionally forgets a few basic rules (it's normal and happens to everyone!), you'll find this brief overview of IRIS basics and all its wonders useful.
Here I'd like to begin a series of articles dedicated to this topic.
There will be eight main topics in total:
Each of them will consist of four parts: Courses, Community articles, Documentation, Applications
This particular part will cover InterSystems ObjectScript. For your convenience, all categories will be hidden under a spoiler.
Back when I was a Developer Support Engineer in the InterSystems Worldwide Response Center (WRC), I would occasionally receive cases involving large message backlogs in a production. The customer would discover that a subset of queued messages were no longer useful and would ask a question similar to the following:
Is there an established best practice for mass-aborting messages in a specific component's queue that match a particular set of criteria?