Making Our Rust/TS Web App Serverless with Pulumi and Python | glowing telegram - Episode 135
In this episode, I continue work on making our Rust and TypeScript-based web application, Glowing Telegram, serverless using Pulumi and Python.
I explore setting up various roles and permissions for tasks running in containers. This involves considering the unique permissions required for tasks like video and audio processing, ensuring they have appropriate access to AWS resources like S3 buckets. I strategize organizing our infrastructure into logical components, determining what makes sense to abstract or isolate into separate files, particularly when considering interdependencies between different infrastructure elements.
I discuss the creation of video and audio processing components, and why separating these concerns makes maintenance and future development more manageable. Throughout, I share insights into challenges like how resource aliases can be used when migrating resources to ensure smooth updates without unnecessary deletion and recreation.
Finally, I cover the process of deploying changes using Pulumi, dealing with artifacts like job definitions, repository names, and ensuring that namespace conflicts are avoided for unique identifiers. This episode is packed with in-depth problem-solving and refactoring strategies as we move towards a more serverless architecture for enhanced scalability and manageability.
🔗 Check out my Twitch channel for more streams: https://www.twitch.tv/saebyn
GitHub: https://github.com/saebyn/glowing-telegram
Discord: https://discord.gg/N7xfy7PyHs