Build your next SaaS product in Go
A step-by-step guide on building a full SaaS web application backend API in Go
Learn how to build an API-first SaaS web application in Go. From initial development to deployment, I teach you how to create a fast and well-tested backend for your next software as a service products.
Get a free sample & pre-order
You can read chapter 8: Billing and subscriptions for free. Leave your email, and you'll be notified when the book reach the next phase - pre-sale.
Pre-order is now available. I decided to give early access to the book after receiving lots of requests. You receive new chapters and changes as soon as they are ready.
$17 for the book and source code
Price increases as new chapter are added.
Why Go in the first place?
Go come with tools that will delight your day-to-day tasks. Things like code formatting, documentation, and tests are all baked in the core.
Use concurrent code when it makes sense. Use all the CPU cores for your app and build high performance web applications.
Go compiles to one single binary with all dependencies. The memory footprint on your server will be a fraction of Node, Ruby, Python, C#, etc.
Table of content
To see which chapters are ready and their sub-chapters go to the bottom of the page. You may also influence the order in which the remaining chapters are released and give your feedback on topics you might want to read about.
|Learn the basics||Advanced SaaS topics|
|1. Let's Go: Create a simple web application to get started with Go.||7. API throttling, limits: Make sure to prevent abusive usage of your API.|
|2. A ~100 lines web engine: We craft ourselves a tiny foundation with no dependencies.||8. Billing and subscriptions: We use Stripe to build a full real-world billing system.|
|3. Tests are important: Balance speed of development and importance of tests.||9. Emails & background tasks: Go routines in all their glory, no need for external processes.|
|4. The data package: MongoDB or PostgreSQL, we're doing both so you pick yours favorite.||10. Capture and replay: Log failed requests and run them against your dev environment.|
|5. API-first my friend: Your users want an API, give them on day 1.||11. Webhooks: You'll have important events occurring, let your users react.|
|6. Authorization middleware: How users are created and how they can authenticate & authorize requests.||12. Automated deployment: We build our own CI in Bash and Go (for real).|
Go is easy to get started.
Are you worried to jump into Go because you've not tried it yet? Are you currently a PHP, Python, Ruby, C#, [insert your language here] developer and would want to know more about Go?
I can assure you that Go will feel comfortable in no time. After one week you should already see great productivity.
This is a sample of the main API code. Our engine is tiny and is more than capable of supporting the needs of a complex JSON web API.
Hopefully you're intrigued and want to jump right away. Pre-order is happening if you want to start reading the chapters that are ready.
I'm openly writing this book and will prioritize chapter that receives the most votes (as much as possible). I'm using my SaaS Roadmap to do this. If you want to be notified when a chapter is ready and want to impact the order in which chapters are released, please follow and clap to show your interests.
If you have feedback or would want to propose topics, please click on the Submit feedback button and let me know your thoughts. I'm not promising that everything will be included, but I'm still flexible at this moment to add or slightly change the table of content.