Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Development and deployment of polyglot systems


Published on

At we are developing a comment plugin for online bloggers and publishers. Since the uptime of our software is very important, we try to apply best practices to our development and deployment workflow. Our system is based on different stacks, which includes the use of different languages like PHP, Scala and TypeScript. This talk is about how we manage the consistency of our data-models through the different stacks, how our SOA is designed and how our continuous integration pipeline works. I'll also show, how we use code generators and shell scripts to automate code creation and tasks. Last, I'll show how we handle our database migrations "on-the-fly".

Published in: Technology
  • Be the first to comment

Development and deployment of polyglot systems

  1. 1. development and deployment of polyglot @3x14159265 systems by david pichsenmeister
  2. 2. charging systems @3x14159265 @3x14159265 startup-founder & tech lead:
  3. 3. @3x14159265 the system
  4. 4. @3x14159265
  5. 5. @3x14159265 why polyglot?
  6. 6. reasons for polyglot ● system is already live ● technologies/skills evolved ● current stack is already a “technical debt” ● get rid of legacy code @3x14159265
  7. 7. @3x14159265 service oriented architecture ● backend only ● choose what service to decouple ● design to use from any language/platform
  8. 8. @3x14159265 possible pitfalls ● use only one(!) message format (e.g. json, xml, soap,...) ● make use of different HTTP request and status codes ● document your internal API
  9. 9. “app oriented architecture” ● thin layer on top of SOA ● form set of features to standalone app @3x14159265
  10. 10. @3x14159265 apps widget platform moderation analytics login
  11. 11. @3x14159265 pros ● easier to maintain/test ● don’t effect your existing codebase ● seperation of business logic
  12. 12. @3x14159265 cons ● over-fragmentation ● repeatedly functionality ● achieve model consistency through all apps
  13. 13. model consistency @3x14159265
  14. 14. @3x14159265 code generators ● define MDL ● use/write codegenerators to distribute models to other languages ● compiler hook
  15. 15. @3x14159265 code generators ● doctrine (php ORM) = MDL ● slick (scala ORM) = generates classes from SQL ● custom code generator: Scala classes → TypeScript classes
  16. 16. continuous deployment @3x14159265
  17. 17. deployment strategies ● always have working branch ● staging environment ● immutable infrastructure @3x14159265
  18. 18. @3x14159265 automation ● automate everything that’s possible ● make use of cloud provider features ● shell scripts are your friend
  19. 19. @3x14159265
  20. 20. @3x14159265 deployment tools SaaS:
  21. 21. database migrations ● some application changes require changes in db schema ● simple and/or risky ● always a pain @3x14159265
  22. 22. @3x14159265 simple changes ● add table ● add index ● add column ● ...
  23. 23. @3x14159265 risky changes ● rename/add column ● change foreign key ● migrate data from one table/column to another ● ...
  24. 24. how we’ve done it ● migrate “on-the-fly” ● create new table for entity to be changed ● “transfer” entity to new table when queried @3x14159265
  25. 25. how we’ve done it ● delete entity on “old” table ● additionally run this procedure as background job @3x14159265
  26. 26. @3x14159265 must haves ● tool, which keeps track of db evolutions ● simple integration into existing project
  27. 27. @3x14159265 must haves ● changelog ● up/down db evolutions ● intense testing ● backups
  28. 28. resources html @3x14159265
  29. 29. resources html @3x14159265
  30. 30. @3x14159265 thanks! feel free to add me on: .../3x14159265