Intro To Spring Python
- 1. Introduction to Spring Python Greg L. Turnquist Senior Software Engineer SpringSource Adapted from presentation given at SpringOne 2008
- 2. What should you take away from this? Spring Python gives you the tools to build dynamic, powerful, easy-to-maintain enterprise solutions
- 3. Who Am I? A test-bitten script junky, always seeking better solutions for customer requirements
- 4. Worked as a software engineer for 11 years at Harris Corporation after graduating Auburn University with Master's in Computer Engineering. Joined SpringSource in 2010.
- 5. Have built mission critical systems, trained on-call support teams, evangelized usage of wikis, and utilized Agile practices to write top quality software
- 6. Active contributor to open source community: MythTV, Mediawiki, Spring Framework/Acegi, TestNG Eclipse plug-in
- 7. Find me at http://www.linkedin.com/in/GregLTurnquist
- 8. Who Am I? Wrote Spring Python 1.1
- 9. Find detailed diagrams, lots of code examples, and information on how to build powerful Python applications using the Spring way.
- 11. The Spring Framework provides many useful features, and I wanted those same features available in Python.
- 12. Agenda History
- 15. Transactions
- 16. Security
- 17. AOP
- 19. Future of the project
- 20. When/where did it come from? In October 2006 came the carputer
- 21. Needed utility of Spring with power of Python
- 22. In December 2006, made first release to Sourceforge
- 23. In July 2008, Russ Miles (SpringSource) invited Spring Python to be a Spring Extension
- 24. In June 2009, started writing Python 1.1 book
- 25. Becoming an extension Since then: Migrated code to Spring's subversion servers, and later to git
- 26. Worked with build team to setup Continuous Integration
- 27. Copied all tickets into JIRA (open and closed)
- 28. Setup Spring Python community forum, blog, and irc channel (#springpython)
- 29. Made 750+ commits; released versions 0.6-0.9, 1.0, and 1.1; closed 109 issues
- 30. Brought on board two more committers
- 31. Currently interacting w/many devs and users about future of Spring Python including roadmap for 1.2 and beyond
- 32. Agenda History
- 35. Transactions
- 36. Security
- 37. AOP
- 39. Future of the project
- 40. We have the same concepts as Spring Simple Object Simple Object Dependency Injection AOP Portable Service Abstractions
- 41. Multiple IoC formats supported Started with an XML-based configuration
- 42. Later, a python decorator-based configuration
- 43. Recently rewrote IoC container, handles: Original format (now called PyContainerConfig)
- 44. Newer, more sophisticated XML format (XMLConfig)
- 45. Spring Java's format (SpringJavaConfig)
- 46. Decorator-based @Object format (PythonConfig)
- 48. New container can mix ANYTHING Allows multiple sources in multiple formats
- 49. Objects can reference ANY other object ...no matter WHERE its defined
- 50. ...and no matter WHAT format its defined in Flexible IoC container + dynamic Python = High Value
- 51. Pure Python IoC @Object-based configuration class MovieBasedConfig(PythonConfig): def __init__(self): super(MovieBasedConfig, self).__init__() @Object(scope.PROTOTYPE)
- 52. def MovieLister(self): lister = MovieLister()
- 56. def MovieFinder(self): return ColonMovieFinder(filename="support/movies1.txt")
- 57. Compare with Spring's IoC Similar concepts found in Spring Java = beans, Python = objects
- 58. @Object is like @Bean
- 59. Current scopes: SINGLETON and PROTOTYPE
- 60. FUTURE: Lazy initialization, auto-wiring Newer concepts not yet found in Spring One-and-only-one container type
- 61. FUTURE: Fluent API (DSL) configuration
- 62. Question What database problem does Python have?
- 63. Answer The Magic 8 says: “Same problem Java JDBC has!”
- 64. Python's database issue For every query: Only difference between every query is SQL and row conversion // open connection to database
- 65. // create cursor
- 66. // execute SQL query
- 67. // for eachRow in resultSet // convert row into an object // close cursor
- 69. Why create DatabaseTemplate? Spring's JdbcTemplate helped me write database queries fast in Java
- 70. Python apps have the same problem and need the same leverage
- 71. DatabaseTemplate should be reason enough for potential users to embrace Spring Python
- 72. ORMs and DatabaseTemplate They provide quick way to persist objects.
- 73. But sometimes they are tricky for complex queries. What if... You need left outer joins that lack foreign key meta-data
- 74. You actually know what a left outer join is and don't need “help”
- 75. You are porting from ORM to another
- 76. You have a DBA team that can optimize your queries
- 77. How to code a query Piece of PetClinic: Use binding variables (?) to avoid SQL injection attacks
- 78. Each row of results is passed to callback
- 79. Notice lack of cursor management? return databaseTemplate.query(""" SELECT id, first_name, last_name, address, city, telephone
- 80. FROM owners
- 81. WHERE upper(last_name) like ?""",
- 82. ("%" + lastName.upper() + "%",),
- 84. Immediate payoff Benefits: No cursors to manage
- 85. No ugly try/except blocks
- 86. Focus is on business logic
- 87. Query will work with any RDBMS* MySQL, Sqlite, PostGreSQL, Oracle (*Okay, DB vendors can support different forms of binding variables, but we are ready for that!)
- 88. How to code a row mapper The other side: Very useful when you have to code a lot of Owner-based queries class OwnerMapper(RowMapper): def map_row(self, row): owner = Owner()
- 95. return owner
- 96. Question Have you ever had to deal with transactions?
- 97. Transactions power the enterprise Database calls are valuable for any app, small or large
- 98. Transactions power enterprise solutions
- 99. Coding transactions is one of the first demands for enterprise apps
- 100. How to code transactions Spring Python makes it easy to programmatically code transactions tx_mgr = ConnectionFactoryTransactionManager(factory)
- 103. class txDefinition(TransactionCallback): def do_in_transaction(s, status): dt.execute("INSERT INTO animal (name) VALUES (?)",('black mamba',))
- 104. dt.execute("INSERT INTO animal (name) VALUES (?)",('copperhead',))
- 106. SELECT name
- 107. FROM animal
- 108. WHERE name like 'c%'", required_type=types.StringType)
- 109. return results print tx_template.execute(txDefinition())
- 111. Declarative transactions are key TransactionTemplate is useful for a handful of transactions
- 112. However, marking business methods with @transactional catapults you into the enterprise
- 113. Decouples business logic from the database
- 114. How to declare transactions class TransactionalBank(object):
- 118. def deposit(self, amount, account_num):
- 119. self.dt.execute("UPDATE account SET balance = balance + ?
- 120. WHERE account_num = ?", (amount, account_num))
- 122. def withdraw(self, amount, account_num):
- 123. self.dt.execute("UPDATE account SET balance = balance - ?
- 124. WHERE account_num = ?", (amount, account_num))
- 125. return amount
- 127. def transfer(self, amount, from_account_num, to_account_num):
- 130. Code is clean and easy to read Declarative transactions move configuration to a central location
- 131. Your logic is clean, concise, and clear to its purpose
- 132. Enterprise apps tend to get HUGE, so maintainable code is paramount to success
- 133. Spring Python's declarative transactions are EXACTLY what you need
- 134. Spring Python 1.1 shows you the pros and cons of programmatic vs. declarative vs. AOP-based transactions.
- 135. Question At what stage do developers code security into their apps?
- 136. Answer HINT: Its usually not the first thing on your mind
- 137. Security done right is hard Security is a big flaw in modern web apps
- 138. Security is typically done last and thus, often rushed
- 139. Rushed implementation = WRONG solution
- 140. Spring Python's security is the RIGHT solution
- 141. Authentication made easy Authenticating a user is EASY
- 142. Uses AOP so your APIs don't change
- 143. Familiar with Spring Security? We borrowed their concepts.
- 144. Makes Spring Python powerful! TODAY: In-memory (for testing), database, LDAP
- 145. FUTURE: X.509, OpenID, OpenSSO, Basic HTTP, 2-factor, anything!
- 146. Authorization also easy Authorizing users is also easy
- 147. Spring Python is just as powerful
- 148. TODAY: Role-based and/or Label-based voters
- 149. + Affirmative- or Unanimous- or Consensus-based policies
- 150. = Powerful, flexible, elegant configuration FUTURE: read-write-execute ACL voters for domain object security
- 151. Anything the community needs!
- 152. Question What technology makes it easy to layer on services without changing APIs?
- 153. Answer Survey says: “ Aspect Oriented Programming”
- 154. Spring makes AOP easy Spring AOP = easy AOP for Java
- 155. Spring Python AOP = easy AOP for Python
- 156. Allows enterprise-style services to be easily built around your objects Security, transactions, auditing, tracing, performance analysis Many parts of Spring Python ride on AOP
- 157. AOP is part of the Spring triangle Simple Object Simple Object Dependency Injection AOP Portable Service Abstractions
- 158. AOP, easy as 1-2-3 class SampleService:
- 160. return "You sent me '%s'" % data service = SampleService()
- 162. >>> "You sent me 'something'" class WrappingSvc(MethodInterceptor):
- 164. return "<Wrapped>" + invocation.proceed() + "</Wrapped>" service = ProxyFactoryObject(target = SampleService(), interceptors = [WrappingSvc()])
- 166. >>> "<Wrapped>You sent me 'something'</Wrapped>"
- 167. Question What can you do to make apps redundant and support more clients?
- 168. Answer The answer behind door #3 is: “ Spread your app across multiple nodes”
- 169. Remoting links things together Remoting is the building block for distributed systems
- 170. It allows you to split up apps that need more resources
- 171. Horizontal scaling allows you to grow your enterprise
- 172. Spring Python allows you to easily supply and consume remote services
- 173. Pyro today, REST & WS tomorrow Today: Pyro (Python remote objects) – pure python RPC library
- 174. Hessian – interoperable protocol
- 175. JMS – link Python-to-Python or Python-to-Java with WebshereMQ Tomorrow: RESTful web services
- 177. Twitter
- 178. Any web service, or other useful remoting protocol
- 179. Other JMS providers
- 180. Agenda History
- 182. Database template
- 183. Transactions
- 184. Security
- 185. AOP
- 187. Future of the project
- 188. Top quality, production-ready Just released 1.1.0.FINAL. Starting 1.2. Has ALL key features needed for development Top quality Tied in to CI: nightly builds and trunk commits
- 189. Built from Day 1 using TDD => Code coverage at 85% Powerful integration CherryPy, Pyro, Hessian, MySQL, PostGreSQL, Sqlite, Oracle Documentation is up-to-date and useful
- 190. Community support is important Solutions What solutions do python users need?
- 191. What 3 rd party libraries can be enhanced or leveraged to provide integrated solutions? Community Striving to answer any/all questions posted to the forums
- 192. Provide fast support to email distribution list
- 193. Grow the community of users
- 194. Spring Python has a strong future Quality is always #1 priority
- 195. Integrating with top-used tools is important Django, Turbogears, Zope/Plone, Paste, Google App Engine, SpringSource Tool Suite, Jython, IronPython Books, podcasts, slide shows, video tutorials, anything to support the community
- 196. Spring + Python = powerful solutions Spring Python provides powerful, dynamic, and easy-to-maintain enterprise solutions
- 197. Useful project links Web site: http://springpython.webfactional.com
- 200. Community forum: http://forum.springframework.org
- 201. Source code: https://src.springframework.org/svn/se-springpython-py/
- 202. Bug tracking: http://jira.springframework.org/browse/SESPRINGPYTHONPY
- 203. Mailing list: http://lists.springsource.com/listmanager/listinfo/springpython-users
- 206. Thank you for your attention