At orat.io 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".
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. @3x14159265
service oriented
architecture
● backend only
● choose what service to decouple
● design to use from any
language/platform
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