Technologies change, requirements change, language availability and viabilities also change. The life of the creative professional (can we really continue to silo ourselves into specific camps such as developer, designer or 'web prophet') has to ...
Source code is nothing other than structured text, much like a CSV file or a phone number. We create software to dissect strings of text and process the pieces all the time, and source code should be no different.
The future of CFML and its related platforms seems to always be in question. Though the question always seems to be answered by the continued persistence, success, and reliability of the CFML platforms themselves; users, administrators, and outsiders alike seem to want to discuss it to no end.
In this session we will introduce the latest tool developed by Rasia and how it has been developed. Since the tool uses a CFML event gateway written in Lucee with CFML, we will go into details of how easy and beautiful it is to write event gateways in CFML with Lucee.
Need to scale? Need to integrate with multiple languages and technologies? Messaging with RabbitMQ will expand your software horizons by scaling your software and technology stack with advanced messaging patterns.
There are several approaches for organizing beans and they all have their pros and cons. We'll go over four different patterns for organizing your model and how they relate historically to languages like CFML and Ruby on Rails.
You've done what you need to do to create a functioning, responsive, good-looking site that works blazingly fast in your development environment. How sure are you, however, that it performs well for your users?
All the buzz in modern Web development seems to be about the client side, yet many tasks still require servers and server infrastructure. Many people use Node.js for their server-side code, but this still requires setting up and maintaining servers.
APIs are at the heart of a vast number of applications, and they are not always written by the development team implementing them. Consuming an external API can be fun but also fraught with potential issues, bottlenecks and nightmares.
Using version control effectively requires a good conceptual understanding of what is happening under the hood. Otherwise when you get stuck, you Google, blindly copy & paste some magic incantation, and pray.
Securing an application by user and role is easy, but what if we need fine-grained control? I'm talking about the kind'a thing github does where you own a repo, and invite others to contribute with varying levels of permissions.
Orchestrating deployments, and managing development pipelines can feel like a maze of infrastructure plumbing. Fear of leaks, or a burst mains leaves the team paralysed, and reluctant to release code as early as possible.