Brian Sappey talks about “How to implement Adobe's API Manager with Swagger, ColdFusion, and API's” in this episode of ColdFusion Alive Podcast.
In this session, you will be provided a look, with examples, about a successful implementation of the Adobe API Manager into a large scale Enterprise environment. You will learn how to configure the API Manager, migrate your existing API's, and create new ones utilizing Swagger. As an added bonus you will learn how to accelerate your SDLC by utilizing API's to automate the API creation process along with the on-boarding of subscribers. Lastly, you will see first hand how to wrap the entire API Manager into a developer portal using, you got it, API's!
- What is the Adobe API Manager?
- Built using Java and Angular
- Comes with CF Entreprise
- SOAP to REST WSDL
- End point level and resource level
- Debugging APIs
- Drill down to problems and solve
- Sandbox and failover server
- Metering and Throttling, SLA
- API key management
- Why should CFers be using it?
- Productivity and Debugging API
- Simplify API creation and consumption
- More control over your API, who uses them and how much they can call them
- What is Swagger?
- How did you migrate to it from Layer 7?
- Cost saving $400k
- Automation and SDLC
- Auto documentation
- Programmatic building of APIs
- Why are you proud to use CF?
- Improvements at Adobe with conference, roadmap
- 30 CF developers at MarketAmerica
- WWIT for you to make CF more alive this year?
- Stronger CF community
- Modern CFML use and use of REST
- Forrester whitepaper
- Be ok asking and talking with Adobe
- What are you looking forward to at CF Summit?
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
- Adobe API Manager
- CA API manager (formerly Layer 7)
- Rakshith Naresh, Adobe Product Manager for ColdFusion
- Swagger– the world’s largest framework of API developer tools for the OpenAPI Specification(OAS)
- WSDL = Web Services Description Language
- Elastic search
- PCI security
- API endpoint
- SLA = Service Level Agreement
- API Contract
- API keys
Brian Sappey is an Applications Architect and Manager of Engineering. His most recent focus has been redesigning the E-commerce infrastructure at Market America/SHOP.com. He is an avid supporter and user of the Adobe API Manager.
Michael: Welcome back to the show. I'm here with Brian Sappey. I hope I’m saying your name that right there Brian. It looks kind of vaguely foreign even though I know you're American.
Brian: yes Sappey
Michael: Sappey, all right. And we're gonna be talking about how he's implemented Adobe's A.P.I. manager with swagger ColdFusion A.P.I. And we'll look at what the A.P.I. manager is and why you should be using it. And what swagger is and how you might use that. And how they migrated from using Layer seven for all these stuff, and some of the big cost savings they had and a whole bunch of automation they're doing in that ColdFusion development using this. So welcome Brian.
Brian: Thank you, appreciate it. Thank you giving me the time.
Michael: Oh! You're so welcome. Thanks for staying up late to do this. I know it's after hours for you. And I know you're off to CF Summit in a few days. So glad you were able to fit this interview in. So tell us what is the… not everyone's use the A.P.I. manager in ColdFusion. Tell us what that is and why we should be using it.