This year marked the tenth anniversary of the Adobe ColdFusion Summit. It was great to get back together with so many familiar faces (and friends!) in person. I’ve attended all of the ColdFusion Summits and, I think, have spoken at all of them as well. I spoke at Summit this year about my favorite topic: ColdFusion and Amazon Web Services.
From: Brian Klaas
I’m grateful that I’ve spoken at Adobe’s ColdFusion Developer Week over the years. This is a great opportunity for those interested in Adobe ColdFusion or the CFML language to get a wide variety of free training about ColdFusion and CFML. I spoke at CF Dev Week again this year about my favorite topic: ColdFusion and Amazon Web Services.
From: Brian Klaas
In spite of the pandemic, the Adobe ColdFusion team held not one but two virtual conferences this calendar year about all things ColdFusion. In addition to helping organize the speakers, I also spoke at both versions of the conference. As usual, I spoke about leveraging the power of cloud-based services to improve on the scalability, reliability, and performance of your ColdFusion applications. This year’s topic was “Scalable, Responsive Apps and Services with Queues and Pub/Sub Mechanisms,” which focused on Amazon Web Services’ Simple Queue Service and Simple Notification Service, both of which are easy to use from within ColdFusion.
From: Brian Klaas
This week, I’m speaking at the ColdFusion Summit 2020 about “Building Serverless ColdFusion Applications with cflambda.” cflambda is a new release from the Adobe ColdFusion team that’s part of ColdFusion 2021 and which lets you write AWS Lambda functions in ColdFusion. There are a number of resources referenced in the presentation that I’d like to share in this post:
From: Brian Klaas
Thanks to the amazing Charlie Arehart for hosting me on last week’s CFMeetup. My presentation — “I Didn’t Know S3 Could Do That!” — covered a lot of the same material that is in my recent series on using S3 in CFML. There were a lot of really good questions, and I very much enjoyed my time delivering the presentation.
From: Brian Klaas
In the last post in this series, we looked at how to add tags to an object uploaded to S3 via the AWS Java SDK. What if you need to change those tags? Are tags the only way to add metadata to objects in S3? Let’s file out.
From: Brian Klaas
As anyone who has worked in any of the major cloud service providers will tell you, there will be ever-increasing sprawl the more you use a cloud provider: more files, more servers, more databases, more accounts, more services, more everything. This is especially the case with object storage like S3. You can easily end up with tens or hundreds of thousands of files in a month. If you were to look at any one of the files in a bucket, could you say who put that file there? Could you look at all the files and be able to charge each file owner for the storage cost? Not without the power of tags.
From: Brian Klaas
When editing files of any kind, users of modern applications expect to have access to previous versions of the file, and undo work that they don’t like or made in error. Implementing a versioning system isn’t easy, especially when file systems are generally set up to only allow one “copy” of any given file. It’s often up to you, the developer, to handle the versioning and ensure that new versions of uploaded files don’t overwrite older ones.
From: Brian Klaas
In the last post in this series, we looked at Lifecycle Rules in S3, how they worked, and how you can use them to save money by automatically moving less-frequently used files to different (and cheaper) storage classes. There’s another powerful aspect to Lifecycle Rules that can save you money: automatically deleting files after a specified period of time.
From: Brian Klaas
In my last post in this series, we looked at using different storage classes in S3 via CFML to save money on long-term storage costs. The use case for that blog post assumed you knew the utilization pattern for the files you uploaded. They would either be very busy files, files that were accessed occasionally, or files that were accessed rarely. What happens, though, when file acess moves over time from frequently access to only occasional access? Wouldn’t it be nice if S3 would automatically move those files from a more expensive storage class with the fastest response time to a storage class where response times were a few miliseconds longer, but cost half the price?
From: Brian Klaas
