While CF2021 has been out now for a year (released in Nov 2020), many orgs may only now be considering moving to it, whether from CF2018 or perhaps CF2016, CF11, CF10, or even earlier. How have the versions changed, in ways that some older code may not run on CF2021? And if you're skipping some CF version/s, what might have tripped you up in those, though not really "new" in CF2021 itself? And what can you do to mitigate such challenges? In this session, CF troubleshooter Charlie Arehart will share from his experience helping folks make such migrations the past year (and for years with previous CF versions), whether in his role as an independent consultant or providing assistance to the CF community. He'll cover things you can consider in advance of the migration as well as things that might help during or after the migration. Most important, this talk will focus on the differences between CF2021 and various earlier CF versions. (Note that he has previously given a talk on migrating CF admin settings, and he plans a future talk on some other aspects of migration.)

Feature flags are a system of enabling certain functionality in your app based on test groups, cross-cutting segments of users, and your internal release processes. Feature flags can be updated on the fly at any time by any user and don't require deploying new code to your servers. LaunchDarkly is a system that helps you manage your feature flags and how they respond to the users of your site. It offers detailed tracking of each user, each flag, and a robust set of rules for determining which users see which features. In this session, we'll see an overview of how to use the new LaunchDarkly SDK which can be used in ColdFusion applications. Demos will include both ColdBox apps and non-ColdBox legacy apps.

Every ColdFusion developer is a builder and an artist. We want to create and craft beautiful, elegant solutions with CFML that are powerful and dynamic... but sometimes, we still need to deal with the legacy code that was built a decade ago by a developer who has long since left the organization and didn't know what they were doing to begin with. Or, maybe the company direction has shifted (again) and what was a priority in the past is no longer relevant. Maybe the approach you originally took to a problem can be done cleaner, and more efficiently. Maybe there's new functionality in ColdFusion that renders old approaches obsolete. At some point, modernization of your approach becomes necessary to retain your sanity! In this group therapy session, I will discuss legacy code, why it's difficult to manage, how to take incremental approaches to improving it and some techniques on how to modernize your development approach.

Most people know that there are differences between CF Enterprise and Standard, most notably the price, of course! But if pressed, I suspect most people could not name more than a couple other differences or perhaps a few, but there are literally dozens. And while you may think you "don't need" Enterprise when it "costs so much more", you may be surprised to find some things that could in fact be "worth it" compared to remaining on Standard: whether from a performance standpoint, in terms of certain tags that are throttled in Standard; or from a licensing standpoint, in terms how many more CPU cores are supported by Enterprise than Standard. It may even be possible that it would be less expensive for you to license CF Enterprise rather than Standard. In this session, veteran server troubleshooter Charlie Arehart will walk through the many areas that there are differences, some having to do with how CFML features may vary, or how CF Admin or even how CFBuilder features may vary. Is CF Enterprise right for you? Or is Standard "good enough"? In this session, it should become more clear for you, or at least you can be more confident/accurate about discussing the differences. Again, there's a LOT of misinformation/misunderstanding, as I watch discussions of the differences in the community. (And yes, of course, many will want to point out that there is the entirely free Lucee engine. If it suits your needs, that's an option. It doesn't suit everyone's needs, so it's not like it's "pointless" to discuss the differences between paying for CF Enterprises vs Standard.) You may even learn about things that are possible in Standard that you didn't know where there, when discussed relative to or indeed as as an alternative to Enterprise-only functionality.

We are excited to let you know that we are racing towards our vision of making Adobe ColdFusion the modernized platform of choice for building cloud native microservice applications with absolute focus on ease of use. The goal of this session is to showcase the progress we have made and help you get a sense of how you can leverage the next version of ColdFusion while you build powerful applications using ColdFusion. Whether you have been a part of the pre-release program or want to try out the public beta, this session is for you. We will covering various pillars of ColdFusion next around cloud integration across AWS and Azure, microservices and modernization of the platform itself. You will also be able to sign up for the pre-release if you haven't already at the end of the session.

Back in the mid 90's we only had one cross platform choice for building internet connected applications and that was HTML, CSS and JavaScript. So why is it now that after 25+ years have passed we are back to building internet connected applications with HTML, CSS and JavaScript and calling them Progressive Web Apps? Join me as we journey from the webs earliest beginnings to get back exactly where we started, or have we? Along the way we'll visit old friends like Flash who was to many the first way to add interactivity to web pages. Discuss the introduction of AJAX where the web started to catch up. Shudder at the seismic shift after the introduction of the iPhone and mobile apps only to be challenged by cross platform mobile development platforms like Apache Cordova. Now, we are back to building plain old web apps and what have we learned along the way and what might be coming next?

Security is a topic we as developers love to ignore as much as possible, but as the number of attacks increase year over year we need to grab hold of the security in our apps. It can be difficult to secure large or legacy codebases, we'll look at some practical approaches to getting in there and making progress. We'll also review some of the top vulnerabilities to watch out for, which also provide a good starting point.

Only a week after your site goes live your client rings you to say that customers are complaining that the site is too slow. A big advertising campaign is booked to go out next week, and what are you going to do about it? Didn't you tell us the performance was fine? (Of course you did some performance tests - well, you got the whole development team to fill in forms and follow links for half an hour on the staging server and nothing seemed to be too slow then - it must be the hosting companies' fault...) You're not alone. A lot of web sites go live without performance testing, either from a false sense of security created by snappy response times in development, a lack of testable performance requirements or not knowing how to translate development response times into production performance. As evidenced by the growing number of high profile Internet service performance stumbles in the last few years, something has to change. In this presentation Robin will describe how to specify performance requirements, and how to relate them to single-user response times in development. To do this he will introduce you to an easy-to-use spreadsheet based on a branch of mathematics called queueing theory that he originally developed while working as a support engineer at Allaire. But more importantly, he will convince you that performance is critical to the success of server applications, and that predicting and fixing performance issues is much easier than you think.

You may (or may not) have heard that CF2021 added (in 2020) a new command-line tool called CFSetup--but first, did you know that it could be used with ANY CF version, not just CF2021? And perhaps you heard its main value is to export/import CF Admin settings via JSON: it can indeed do that, and while that may excite some, others may yawn if they've "seen that elsewhere". (To be clear, it can export/import either ALL settings or selected ones.) But did you know it could be used for far MORE than that alone? And did you know that those exported json config files could be used to set the admin configuration on startup of CF 2021 Docker images. Even if not using Docker, the tool can be a boon for all sorts of automated deployment of CF--again any CF version. And did you know you don't even need to install CF2021 to use it? While the feature is well-documented (and offers its own help), who has time to read the docs, right? In this session, veteran CF troubleshooter Charlie Arehart will present and demonstrate the key capabilities of CFSetup, as well as others that may surprise you. He'll also conclude with a brief discussion of the similar (but different) tool, CFConfig, a plugin for Ortus Commandbox. He'll touch on the question of why one might choose one over the other (it's ok to use either or both with the same CF instance). He'll also contrast these with the much older CF "CAR" Admin migration tool. Each tool has its value for different needs.

We did it, reaching episode 300! Join us as we celebrate this momentous anniversary. The Online CFMeetup was formed in 2005 and has been hosted since 2007 by Charlie Arehart, with sessions from over 150 speakers on a wide range of topics related to CF. In this session, we'll celebrate the past and look to the future for the group, where I will propose a new direction/format. All still about CF, of course. Here's to 300 more!