Summary: Overall, the webinar was a solid review of a a pretty significant shift for Adobe's ColdFusion 2020 (microservice/cloud/modernization). Though playing a bit of catch-up on a few fronts, as highlighted by the animated color commentary in the chat, this version is going to be a game changer.
These are my notes from the CF2020 release webinar with Rakshith.
The new installer size is far smaller/granular, which works well on a local installs and cloud deployments and everything in between. As far as modularity is concerned in the new release, Adobe is breaking CF up into "tiny" modules to install/deploy, which I liken to the current installation wizard that allows you to install features by ticking boxes, etc. but far more granular. They also demoed as part of this a CLI. I've become familiar with Ortus's CommandBox and the power it wields, and Adobe's cfpm allows you to get really fine tuned in your deployment. It will be interesting to see how licensing works here. I'd love to deploy our applications to the cloud and release our network department from all of the permissions, security, and other hangups associated with hardware maintenance.
There were robust comments in the chat calling for more fully documented cfscript, lamenting on the lack thereof. While that has historically been true, I believe Adobe and the Community (and also Lucee) have come a long way in terms of the documentation. We've got the cfscript ColdFusion Cheat Sheet by Pete Freitag, the CFScript Syntax Guide CFML Documentation, CFScript.me , and let's not forget cffiddle.org. Honestly, I'm a bit blown away by what this small yet mighty community is doing, and not just with CFScript, all of which is documented at Charlie's http://www.cf411.com/cfhelp.
Back to the Adobe's package manager, CFPM which is inspired by the NPM package manager. Sooo, does the sql sever module install the odbc connectivity to MSSQL datasources? I think it does. So if I don't have Oracle datasources, I don't have to install it? That's interesting. CFPM will spit out to the package manager all required modules per the code scan. I think the json file will contain all settings and requirements, and Docker will support this. I kind of got into the weeds here in terms of its use, because a lot of this stuff we currently do not use, but for now, it's cool to see how using CFSetup from the cli, you can do many things, like exporting the settings for portability.
One of the more interesting links featured in the chat from Elishia Dvorak was the deprecated features page. I wonder - does CF Builder's code tools (code scan) check for all of these? Last I checked, I think it does.
CF Installs in the cloud. In AWS, storage is called S3, and with Azure, it is called Blob. It is very simple to move from one to another. Around the time Rakshith opened up CF Builder, the superiority of VS Code was the topic of conversation in the chat. I have heard that Adobe was considering officially supporting VS Code, and I have to agree that this would be a good thing considering the CF Builder bloat. At that time, Elishia confirmed that they are working on support for VS Code to go along with existing plugins. But this would have to include the code review/security solutions moved to VS Code as we use these features in Builder as part of our procedures.
I love how Adobe is borrowing from other successful implementations from other languages and platforms. It's good to be inspired - you find great solutions, and imitation is the sincerest form of flattery.
As I watch the demo, I've got one eye constantly on the chat, which is turning out to be just as interesting. Charlie is calling for an AMA session with Adobe, and Rakshith is promising to address questions at the end of the session. I am looking forward to seeing how this webinar ends!
CF 2020 cloud is at home on both AWS and Azure (storage, database, noSQL, caching, messages/notifications). Not tied to either interface - same code across AWS and Azure. Rakshith shows how this is handled with some code
Other improvements discussed include language updates, of which Lambdas lead the list.
That is it for Part I.