The document discusses different communication channels for heterogeneous environments including databases, webhooks, publish/subscribe, and RPC. It then evaluates several queue systems like ActiveMQ, RabbitMQ, and Faktory. Faktory is recommended for simple interconnections due to its easy setup costs, support for most languages, and ability to handle around 1,000 requests per second. For more requests, considerations include required speed, available resources, whether an MQ server is acceptable, and language support requirements.

1. GO IN HETEROGENEOUS
LANGUAGE
ENVIRONMENTS
Oleksandr Simonov

2. ABOUT ME
17 years in IT
Addict of Programming
Languages Polyglot
OpenSource contributor

3. HETEROGENEOUS
ENVIRONMENTS

4. USING HARDWARE AND
SYSTEM SOFTWARE FROM
DIFFERENT VENDORS

7. WHAT IS WRONG?

8. COMMUNICATION

9. COMMUNICATION
CHANNELS
• Database
• WebHook
• Pub/Sub
• RPC

11. DATABASE
• Easy to use
• Transactions
• Slow
• Hard to maintain

13. WEBHOOK
• Fast
• Flexible
• Secure
• Hard fallback logic
• Connection issues
• No retries

15. PUB/SUB
• Message Oriented
• Channel based
• No persistance
• Oriented on real-time
messages

17. RPC
• Many
Implementations
• Binary protocols
• Secure
• Need to wait on
response
• No persistance

19. ANY BETTER SOLUTION?

21. QUEUES SYSTEMS
• ActiveMQ
• RabbitMQ
• Faktory
• NSQ

23. HOW TO CHOOSE?
• Setup costs
• Support costs
• Implementation costs
• Hardware costs
• Benchmark

24. SETUP COSTS
• How much time required to run it locally?
• How must time to run in production?
• Multi-Nodes support?

25. SUPPORT COSTS
• How stable is it?
• How to catch errors?
• Fault-Tolerance?

26. IMPLEMENTATION COSTS
• Does API is easy to use?
• How clients documented?
• Supported platforms and languages?

27. HARDWARE COSTS
• Does it required a lot of resources?
• How it deal with big amount of requests?
• Data recovery? Backups?

28. BENCHMARK
• Run a stress testing with limited resources
• Run a stress testing with ultra power
resources
• 99% percentile of overload test

29. FAKTORY
• Sidekiq like behavior
• Easy to start
• Best option for simple interconnection
• Clients for most usable languages

30. FAKTORY
• Used in 3 projects which related to
marketing/advertising automation
• We have connected Ruby, Go, PHP in one
ecosystem
• Nice UI to check what is going
• ~1000 req/second

31. HAVE MORE REQUESTS?
• How fast you need to proceed them?
• How much resources you will have for them?
• MQ Server is ok for you?
• Can you say bye for other languages?

32. QUESTIONS?