· Sep 11, 2020

InterSystems Full Stack Contest

Hey Developers!

We're pleased to announce the next competition of creating open-source solutions using InterSystems IRIS! Please welcome:

⚡️ InterSystems Full Stack Contest ⚡️

Duration: September 21 - October 11, 2020


1. Experts Nomination - winners will be determined by a specially selected jury:

🥇 1st place - $2,000 

🥈 2nd place - $1,000 

🥉 3rd place - $500

2. Community Nomination - an application that will receive the most votes in total:

🥇 1st place - $1,000 

🥈 2nd place - $500 

If several participants score the same amount of votes they all are considered as winners and the money prize is shared among the winners.  

Who can participate?

Any Developer Community member, except for InterSystems employees. Create an account!

Contest Period

September 21 - October 4: Two weeks to upload your applications to Open Exchange (also during this period, you can edit your projects).

October 5 - 11: One week to vote.

October 12: Winners announcement.

The topic

💡  Full Stack Applications 💡

Develop a Full Stack solution using the InterSystems IRIS. By full stack we mean a frontend application web or mobile which uses data in InterSystems IRIS via REST API, Native API, JDBC, or just IRIS Web Gateway.

The application should work either on IRIS Community Edition or IRIS for Health Community Edition or IRIS Advanced Analytics Community Edition.

The application should be Open Source and published on GitHub.

If the application satisfies some additional requirements listed in this post, it gets additional technology votes.

Helpful resources

1. InterSystems IRIS Docker templates suitable for a Full Stack application:

2. How to submit your app to the contest:

3. Online courses:

4. Videos:


Please find the Judgment and Voting Rules for the Contest here.


Ready. Set. Code.

Please join our exciting coding marathon!

❗️ Please check out the Official Contest Terms here.❗️

Discussion (22)3
Log in or sign up to continue

Yes, it would be possible to do so - it would be a simple matter of writing a process that invoked the appropriate Conduit REST APIs to create the articles, comments and links to authors/users from your data export.  The one thing that might be tricky would be the user password property, which would be required for a user to log in and view/edit their own articles, and to follow other users and/or favourite their articles.