Wow, I didn't know that, and I never even considered the possibility of using regular expressions in the map! Very interesting, thank you!

It's true that using streams makes handling large volumes of data easier; however, I had problems some time ago with an API response because, to read JSON objects within a stream, I needed to transform them using %FromJSON, but due to the volume of data, this caused a StringStack error. Therefore, I had to read the stream line by line and extract the data using pieces and extracts.

Many years ago I used Xecute in some very specific situations that, I confess, I don't even remember very well anymore; however, I remember very well that debugging legacy code is always made more difficult with the use of Xecute, so I have always been an advocate against using it, except in situations of extreme necessity. 
But I recognize that in your example it really seemed quite useful.

That's great, I'm actually working with Streams right now, because in interoperability scenarios it's very common to receive a very large amount of data.

Thank you for sharing your experience. It reminded me of my beginnings; I've been working with Mumps since 1989, when it was still a standalone system, and soon after, based on HP UX Risc servers. The biggest challenge at the time was working with integrations via telephone calls and RS232 RS485 TX/RX protocols. It was a period with many needs but few resources and possibilities available.

It's great to hear praise for ObjectScript coming from a Python "native"...  :)

I liked your comparison between Functional and OOP; I've also had situations where direct functional access to data performed better than an SQL query.

Within an ObjectScript structure, direct access via globals - although no longer very common - is very fast, and especially useful when you have a very large number of subscripts for the same node, and you only want to know the value of the last subscript, in which case you can simply read using the reverse $Order (equivalent to ORDER BY ... DESC or MAX(), however, without needing to construct an SQL read method), especially if you have a mapped class.

Wow, this is a very interesting guide! The last time I needed to switch computers, I redid all the connections manually.

Hi! The complete code example makes it much easier to understand, thank you very much!

It's great to see you mention MUMPS, which has always been praised for integrating applications and databases in a very natural way, and the evolution to IRIS has made this integration even easier by incorporating other languages ​​and native interoperability.

I really liked the way it was structured; it was very easy and didactic! Extremely simple for those who need to take their first steps in IRIS technology!

Very practical, I continue to use it as a reference, thank you very much!

It's a unique opportunity to discover the latest innovations in the world of technology.

Done! Thank you!

Trying to understand a bit more about AI, going beyond just using prompts.

This article came at a good time, we were discussing services related to RabbitMQ just a few days ago. Thank you very much!

Thank you, that's very practical!

Congratulations to everyone!

Thank you, it's very informative and well-exemplified!

Congratulations to the Developer Community!!! Bring on the next 10 years!

Nice article! I did a simple count test on a table with approximately 75,000,000 rows, and the time dropped from 22 seconds to 6 seconds using %PARALELL. Thanks for reminding that it is available. We don't always remember to use it, but we should... :)

Great article! I've been using JWT for a little over a year, but I had some difficulties implementing it fully at the time. An article like yours is very helpful in clarifying some doubts!

That's fantastic! Congratulations @henry !

Great! I've only been using JWT on IRIS for a short time, but it's very practical!

Congratulations to all participants and winners!

Congratulations! And thank you for taking the time!