Chapter 5 Secure Your Services
Distributed Services with Go — by Travis Jeffery (38 / 84)
👈 What You Learned | TOC | Secure Services in Three Steps 👉
When you build a project, your goal is to solve a problem. You may get so focused on this goal that you ignore the other factors you should consider, like security. Security is one of those things that’s super important but easy to ignore.
Yes, creating a secure solution is more complicated than building a solution without considering security. But if you want to build something that people will actually use, it has to be secure. And it’s far easier to incorporate security from the start than it is to retrofit security into a finished project. So you need to keep security in mind from the very beginning. In this book, for example, we don’t just want to build a tool to stream data — we want to build a tool that streams data securely.
When you start your career as a software engineer, security can seem like a thankless job. If you do it right, no one will know you did it at all, and building it can be scary and even boring at times. Over the years, from building several software-as-a-service startups, I’ve changed my tune — I now consider securing my services as important as the problems they solve. Here’s why:
- Security saves you from being hacked. When you don’t follow security best practices, breaches and leaks follow with amazing regularity and severity, as we’ve seen in the news. Whenever I’m…