Observability and Troubleshooting in Forge
1 like8,274 views
The document discusses the evolution of software development from bare metal servers to virtualization, containers, and serverless functions. It notes how debugging and observability have become more difficult as software moves to remote "somebody else's computer" environments. The author introduces Forge as Atlassian's solution for providing developers a declarative language and best-in-class experience for building user interfaces on serverless infrastructure, including features for debugging, monitoring, and security.
Observability and Troubleshooting in Forge
- 1. JAMES HAZELWOOD | I’M A DEVELOPER, NOT A SPEAKER! | USS ATLASSIAN Observability and Troubleshooting in Forge
- 2. Software is a frontier
- 3. Software is a frontier The "bare metal” age Virtualization IaaS (AWS EC2) PaaS (Heroku) Containers (Docker) 1990s 2000s 2006 2009 2013 LOTS of Containers (Kubernetes, etc) 2013- 2014- FaaS (AWS Lambda)
- 8. Live reload
- 9. Dashboards & log search
- 12. “Somebody else’s computer” Something else
- 13. “Somebody else’s computer” Something else “Somebody else’s computer” Something else Somebody else’s something else
- 14. No, you can’t have our AWS password (sorry)
- 15. Clicking around
- 16. `console.log`
- 18. Live reload
- 19. Dashboards & log search
- 20. 😱
- 21. 😅
- 22. Forge Forge UI Developer ExperienceAtlassian Hosting Functions-as-a-Service (FaaS) A declarative, cross- platform language for defining user experiences Provide the world’s best ecosystem developer experience
- 23. Clicking around
- 26. `console.log`
- 28. Live reload
- 29. Tunnels!
- 37. 🖖
- 38. JAMES HAZELWOOD | FAAS FEATURE LEAD | USS ATLASSIAN Thank you!