Visit our site to listen to past episodes, support the show, and sign up for our mailing list.
Service integration platforms have traditionally been the realm of Java projects. Zato is a project that shows Python is a great choice for systems integration due to its flexibility and wealth of useful libraries. In this episode we had the opportunity to speak with Dariusz Suchojad, the creator of Zato about why he decided to make it and what makes it interesting. Listen to the episode and then take it for a spin.
- Hello and welcome to Podcast.__init__, the podcast about Python and the people who make it great.
- Subscribe on iTunes, Stitcher, TuneIn or RSS
- Follow us on Twitter or Google+
- Give us feedback! Leave a review on iTunes, Tweet to us, send us an email, leave us a message on Google+, or leave a comment on our show notes
- I would like to thank everyone who has donated to the show. Your contributions help us make the show sustainable. For details on how to support the show you can visit our site at
- I would also like to thank Hired, a job marketplace for developers, for sponsoring this episode of Podcast.__init__. Use the link hired.com/podcastinit to double your signing bonus.
- Linode is also sponsoring us this week. Check them out at linode.com/podcastinit and get a $10 credit to try out their fast and reliable Linux virtual servers for your next project.
- We are recording today on October 27th, 2015 and your hosts as usual are Tobias Macey and Chris Patti
- Today we are interviewing Dariusz Suchojad about Zato
Interview with Dariusz Suchojad
- How did you get introduced to Python?
- Can you explain what Zato is and what motivated you to create it?
- What makes Zato stand out from other service bus implementations?
- What are some signs that someone should consider incorporating Zato into their software architecture?
- Does zato perform well in restricted resource environments like ec2? What performance bottlenecks are common when using zato?
- It seems that most other ESB projects are written in Java. What advantages does Python have over Java for this kind of project and in what ways is it inferior?
- The architectural nature of ESBs are such that they form the central backbone of a software system. How have you been able to ensure an appropriate level of reliability and stability in Zato while still delivering new features and improvements?
- What are the scalability and high availability characteristics of Zato?
- Does zato run well using pypy?
- For anyone wanting to use Zato, what are the infrastructure requirements for deployment?
- What are some of the security ramifications you took into account in zato’s design?
- What are some of the most novel uses for Zato that you have seen or heard about?