4 Things You Should do for All Outbound Calls
You're tasked with calling another system from your app. You have the code written, you're parsing the bytes from the wire. But are you done? I assert that there are four more things that you should seriously consider every time you talk to a remote system. These things protect your system, the systems you call and give visibility into your system, the systems you're calling and the network.
These concepts can be universally applied to any stack wherein you call out to another system that is not under your control but we'll use a simple Grails application as a basis for our examples. All the frameworks shown are available for use in other JVM languages.
About Demian Neidetcher
Demian Neidetcher is a Senior Engineer at Time Warner Cable working on customer portals and getting television content to IP devices. He first got the programming bug staying up late nights with his Commodore64.
He has been professionally writing software for over 15 years. Most of his experience is with JVM languages (Java, Scala, Groovy) in the telecommunications domain doing things like inventory systems for a long-haul carrier, integrating conferencing software and routing VoIP traffic including geo-spatial 911 call routing. He has worked for companies ranging from Fortune 500 to small start-ups. In every environment Demian has looked for pragmatic approaches, solutions and process to get teams delivering software that benefits users.
More About Demian »