Jon Clausen talks about “Portable CFML with Cloud deployments, Microservices and REST” in this episode of the ColdFusion Alive Podcast, with host Michaela Light. Jon is one of the speakers for the upcoming Into The Box ColdFusion Conference, where he will talk about Hall PaaS: Cloud CFML deployments with CommandBox and Bringing Legacy Apps Back To Life with Box Microservices.
- Hall PaaS: Cloud CFML deployments with CommandBox
- Small container
- What is PaaS and why would you want to use it?
- Platform as a Service
- How you you save DevOps headache with smart cloud deployment
- Will talk about the options for using container-based PaaS solutions such as Heroku, Dokku, Kubernetes, etc for quickly standing up and scaling environments
- How to implement on demand or scheduled scaling
- Bringing Legacy Apps Back To Life with *Box Microservices
- what is a Microserver
- Monolithic code vs microservice architecture
- maintainable. portable and scalable
- How to overcome resource intensive sections of your code using microservice
- Easier to rewrite
- Why box microservices?
- rapid from concept to deployment
- easier deployment
- Why are you proud to use CF?
- most portable
- efficient resource use
- WWIT to make CF more alive this year?
- talk it up
- easy and pain free development
- RESTful services 1-day workshop
- What is REST?
- representational – JSCON or XML from you model
- Why Stateless matters?
- Portable API pattern
- Scalable API pattern
- binary internal REST transfer
- Logic deduplication
- Versioning of API
This workshop is designed for beginning or intermediate ColdBox developers and focuses on the understanding and implementation of RESTful applications, modules, and microservices. At the end of the workshop, the participant will have developed a working RESTful API service which can be used as a baseline template for their own future development needs. The API service will be scaffolded and implemented using a variety of readily-available tools, such as CommandBox and the ColdBox REST application skeleton.
What are you looking forward to at Into The Box conference?
And to continue learning how to make your ColdFusion apps more modern and alive, I encourage you to download our free ColdFusion Alive Best Practices Checklist.
Because… perhaps you are responsible for a mission-critical or revenue-generating CF application that you don’t trust 100%, where implementing new features is a painful ad-hoc process with slow turnaround even for simple requests.
What if you have no contingency plan for a sudden developer departure or a server outage? Perhaps every time a new freelancer works on your site, something breaks. Or your application availability, security, and reliability are poor.
And if you are depending on ColdFusion for your job, then you can’t afford to let your CF development methods die on the vine.
You’re making a high-stakes bet that everything is going to be OK using the same old app creation ways in that one language — forever.
All it would take is for your fellow CF developer to quit or for your CIO to decide to leave the (falsely) perceived sinking ship of CFML and you could lose everything—your project, your hard-won CF skills, and possibly even your job.
Luckily, there are a number of simple, logical steps you can take now to protect yourself from these obvious risks.
No Brainer ColdFusion Best Practices to Ensure You Thrive No Matter What Happens Next
Modern ColdFusion development best practices that reduce stress, inefficiency, project lifecycle costs while simultaneously increasing project velocity and innovation.
√ Easily create a consistent server architecture across development, testing, and production
√ A modern test environment to prevent bugs from spreading
√ Automated continuous integration tools that work well with CF
√ A portable development environment baked into your codebase… for free!
Learn about these and many more strategies in our free ColdFusion Alive Best Practices Checklist.
Mentioned in this episode
Jon Clausen hails from Grand Rapids, Michigan and has been developing CFML applications for over a decade. He was born and raised in South Dakota and attended SDSU and DePaul University. In 2004, after 14 years with a Fortune 100 company, he founded Silo, a full-stack development and technology consulting firm in Grand Rapids, Michigan.
After hours, Jon enjoys theater, fishing for smallmouth bass on the Great Lakes, and chauffeuring his 12-year-old daughter back and forth to the horse stables.
He is pleased to represent Ortus Solutions as a product evangelist for the Box products and is eternally grateful for tools like ColdBox and CommandBox, which continue to evolve and demonstrate a bright future for CFML development
(* WWIT = What Would It Take)
Michaela Light: Welcome back to the show. I'm here with Jon Clausen. I hope I'm pronouncing that right, Jon.
Jon Clausen: Clausen but close enough.
Michaela Light: Clausen, all right. And he's the president of Silo Webworks and a part of the artist team and he's going to be speaking into the box and we're going to talk about portable CFML with cloud deployments, microservices and rest, and he's actually giving two talks, and he's also giving a whole day workshop, so we're going to talk about all that in this episode. We're going to start off by looking at platform as a service, and how you can save devop headaches with SmartCloud deployments and different options there are for container based PAS solutions, and also we'll look at how you can use microservices to take a monolithic legacy app and cut it up into microservices so that it is more maintainable and portable and scalable. And some clever ways that Jon has for overcoming resource intensive sections of the code in an app, so they can scale out separately from the rest of the app.
Then also, we're going to look at REST architecture, and why that works so well and why it has to be stateless. So welcome, Jon.
Jon Clausen: Thank you.
Michaela Light: So let's come back to the beginning of that, you're talking about PAS, which stands for Platform Assess Service, so why would someone want to use that, or what exactly is it?
Jon Clausen: Well, Platform as a service is basically implemented in different ways across different providers. So you've got your for pay proprietary providers such as ABS Cloud services, Google Cloud services, Hiroku. You also have open source options open to you as well. So you have for example, Doku, which is basically Hiroku, an open source version of Hiroku. You have Kubernetes which is a google product that is continuing to evolve and a lot of people are really adopting that. You've got front ends also for Kubernetes as well, that will allow you to do bill packs, there's a product calls BASE that works with Kubernetes that way. And you also have Dr. Swarm, which is Dr.'s own native implementation. And what a platform as a service does, is it abstracts the whole details of the container layers, and allows for easy deployments, sometimes scheduling, management and orchestration of containers against one or more servers.