As software architects, we usually have a few parameters when designing a solution for an upcoming feature. Those parameters might be delivery time, maintenance and extensibility. But we often forget about one crucial parameter: cost.

When your team keeps cost in mind, you start exploring new tools that you didn’t even know existed. So in this process, you learn about new technologies and you start thinking more about efficiency rather than sticking with what you know.

In this session, I'll explain how we adopted a culture of considering costs, how we track the cost of our production environment and how in three days we started saving $25,000 per month. I’ll also discuss how thinking about money expanded our team’s knowledge in new and up-and-coming technologies.