@Timothy Leavitt - did you notice that he is looking to launch a window from the SMP via UserAction?  

Great tip ... I never knew this!!  Thank you for sharing as this always bugged me not to he able to use these keyboard shortcuts:)

Great tip ... I never knew this!!  Thank you for sharing as this always bugged me not to he able to use these keyboard shortcuts:)

Thank you for the very thoughtful article @Robert Cemper !!  Definitely some good ideas to muse on .... 

I completely agree with @Timothy Leavitt here.  Besides the speed of the DB, the core value of Caché (now IRIS) for the past 2 decades that I have used it has been the ability to create just about anything I needed within an application without needing to bolt on additional tools, additional layers, additional languages, or additional dependencies.  Directly access business logic on the server from the web page, directly instantiate and work against objects anywhere in your code - there is no 'throwing things over the wall' to the DB guy, or to the microservice guy, you just code what you need in ObjectScript and be done with it.  
To @Robert Cemper 's point below, I really don't think it takes an Artist to be able to write and support this kind of code, just a talented developer with some good OO skills.  I do think you need to be able to find Artists to support the legacy M applications which are still floating around, but it is pretty straight-forward to get the full power of the stack for new applications while avoiding modes of use which would require a "Priest" to be able to interpret it in the future.  
Having recently been involved in another initiative for several months that was not DB-centric development, and having witnessed how much harder it seemed to be and more time intensive to piece together the different disparate technologies at different levels of the stack in order to make a full solution, it reminded me of why I fell in love with Caché in the first place and made me excited to get back to full stack dev in on a single integrated platform :)  
 

Thanks for the heads up @Bren Mochocki!  This is being looked into as we speak.  No eta on when it will be restored as of right now....

Thanks @Fabiano Sanches  - looks like great resources to help get people out of the gate more quickly!

Great recommendations and very helpful with the screenshots - thank you @Anastasia Dyubaylo  :)
 

Great article @Yuri Marx Pereira Gomes !!  Really good practical suggestions for these areas of security focus.  Thank you!

really excellent course!  and Joel is a great teacher!!!

@ROBSON SERPA DA ROSA  - welcome to the Community!!

The two options available to you are InterSystems Studio (ships with Caché and is an install-time option) and VS Code with appropriate add-ons.

InterSystems Studio is being phased out (no new dev) - the future is VS Code, so I suggest you start there.

This may be a good place for you to start: https://community.intersystems.com/post/webinar-introduction-vscode-obje...

Hope that helps!!

Great article, thank you!  I hadn't seen the DataOps concept before but it makes a lot of sense.

Really excellent article Anton- I learned a lot,  thank you for taking the time to put it together!!!

really helpful trick!  thanks for sharing @Alex Kogan , I didn't previously know this was an option :)

Great work on this Matt!  Thank you for your hard work to bring this enhancement to our Beta Users!!

Great data point!  Thanks @Dmitry Maslennikov :)

The nice advantage of storing them in the DB is that is makes the following easier:

- refreshing earlier environments for testing
- mirroring the file contents
- encryption
- simpler consistent backups

However, if you're talking about hundreds of GBs of data, then you can run into issues which you should weigh against the above:

- journaling volume
- .dat size
- .dat restore time

One way to help mitigate the above for larger volume file management is to map the classes that are storing the the stream properties into their own .DAT so they can be managed separately from other application data, and then you can even use subscript level mapping to cap the size of the file .DATs.  

Hope that helps