“Managing servers is fun” – No developer ever. Moving to a cloud environment can be awesome and beneficial if done right. But it can also be expensive and a real pain if done wrong. What we found in building apps on cloud platforms, which pitfalls we encountered and when it’s suited an when not.

1. Cloud-Tastic
Learnings from moving into the cloud

2. Ivan Sieder
Lead Engineer @ SiMedia.com
@ivansieder
Ifan, Aifan, Aiban, Aiven

6. Daniel Stori { turnoff.us }
Thanks to Michael Tharrington

7. Daniel Stori { turnoff.us }
Thanks to Michael Tharrington

11. CREATE A
PLAN
JUST
DO IT

12. Preparations

13. =>"

14. =>"

15. Let’s do it!

18. Plan ahead
Which host operating system and version will
your containers run on?

19. docker pull microsoft/aspnet:4.7.2-windowsservercore-ltsc2016

20. 14GB

25. X-Forwarded-For
Logging, whitelisting,…

26. Server-Sessions
Avoid them, or use sticky sessions, or JWT?

33. Start small
Don’t thrive for docker-compose at the beginning,
start off by using single docker files and when
everything is stable, go for compose.

34. Scaling
Some apps might take longer to start, consider this
when setting scaling limits (scale earlier, as it
might take longer for the container to start)

35. Health Checks
Some apps might take longer to start, consider
setting higher timeouts to avoid unnecessary
container recreations

36. Short-term pain
Long-term gain
It’s difficult to completely set up a cloud
environment initially, but it provides a lot
of benefits, even for “legacy” applications

37. Just do it!
Don’t try to learn all about every part of a
cloud provider, look up what you need, when
you need it.

38. Less server management
More software development

39. Thank you!
ivan@sieder.xyz - twitter.com/ivansieder