Nathaniel Francis talks about “The best REST you've ever had: ColdBox REST” in this episode of the ColdFusion Alive Podcast, with host Michael Smith.
Nathaniel is one of the speakers for the upcoming Into The Box Conference where he will talk about The best REST you've ever had: ColdBox REST.
- Why REST over regular CF
- Separate front end from data
- Easy to support multiple platforms such as phone, desktop, and IoT
- Why the CB REST API
- CB, CF Wheels, ACF, Node
- Move to CB REST is easy Converting from CFM to REST
- SQL Hibernate ORM -> REST
- REST and CouchBase Lightweight Star Wars app
- Why are you proud to develop in CF?
- WWIT to make CF more alive this year?
- What are you looking forward to at Into The Box?
- Nathaniel Best SciFi books End Game and Dune, or a Git merge of both!
- 03:10 Separation of concerns is good on development teams as well. Whereas we like to talk about being full developers and knowing everything from being a sysadmin and a database expert to a backend data modeling expert, to doing cool things in the browser, the truth of the matter is people are really good at certain things.
- 04:38 having a front end and a distinct back end, it sounds like a much larger thing, but with the plethora of different ways they're deploying front ends these days, I think having a REST API backend gives you something to ease the mind of the presentation and lets that be its own animal, so to speak. It works better in the end.
- 14:32 I still believe that a lot of traditional developers will use ORM and use SEQL. Those are solid and tried and true methods. This will give them an opportunity to see something different, something that's a little bit lighter.
- 16:41 I'm proud to develop in ColdFusion, because it has the combination. Specifically, being a part of the ColdBox and a lot of the open source community as part of ColdFusion, because we have two things
- 18:31 I know some people I've talked with, they think ColdFusion is old. There's a lot of things that are old. Being old doesn't necessarily mean you're not good. In fact, being old means that you've been tried and true in some ways. The question is whether you're moving forward.
Mentioned in this episode
Michael Smith: Welcome back to the show. I'm here with Nathan Francis. We're going to be talking about the best REST you ever had. That's not a nap. That's rest as in ColdBox REST. We'll also be looking why you might want to use REST instead of doing regular ColdFusion and why ColdBox is the best REST. Nathan has used a whole slew of different REST APIs. He's got a lot of experience there.
We'll also look at how, if you need to convert between REST APIs, or convert from regular ColdFusion code to REST, how easy it is to do that. Also, we'll look at a cool project he's been working on using REST and Couchbase, which is a really light weight setup he's got. Welcome, Nathan.
Nathaniel F.: Thank you, sir. Glad to be here with you.
Michael Smith: I think we better start with the big question in the room, which is why should anyone use REST instead of regular ColdFusion? A lot of CF developers don't even use REST.
Nathaniel F.: Yeah, that's very true. I think part of that comes from CFML's heritage itself, which CFML excelled. It was one of the main languages that excelled at making just full bodied applications dynamically. Since it thrived in that area, when the tech industry moved to some newer ideas, it had a good sweet spot.
ColdBox has allowed CFML to really move forward. One of those ways is with REST APIs. What that provides is instead of these full bodied, traditional applications, you can make something that anything can touch. You can use any type of front end technological mobile obviously is universal now, even things all the way down to the watches and the Internet of things to be able to talk to a REST API.
That really makes your program universal. That bounds to the traditional sweet spot that CFML has traditionally been in. REST APIs are versatile. That means when you write something, you know it can reach a lot farther than just the browser that it used to.
Michael Smith: If you wanted to swap out a different front end, that would be really easy to do?
Nathaniel F.: Yes, absolutely. It'd be very easy to do. What that does is it makes both ends of your application able to go through phases. If you wanted to freshen up your front end, your back end is solid with the REST API setup. You can even your REST API itself to have updates to it, completely independent of the front end.
About the speaker
Nathaniel Francis is an employee of Computer Know How, the Wisconsin-based technology firm and ColdBox Alliance Partner. He has been working with ColdBox since he started at CKH in September of 2012. His focus is on ColdBox applications, ContentBox sites, and ColdBox REST apps. He is a husband, father of 8, worship leader, theologian, scifi enthusiast, and balding.
Learn more about Nathaniel Francis at:
PS What are the first steps you take for preventing the ColdFusion project problem? This awesome Checklist is the best next step…