Book Image

Python Web Development with Sanic

By : Adam Hopkins
Book Image

Python Web Development with Sanic

By: Adam Hopkins

Overview of this book

Today’s developers need something more powerful and customizable when it comes to web app development. They require effective tools to build something unique to meet their specific needs, and not simply glue a bunch of things together built by others. This is where Sanic comes into the picture. Built to be unopinionated and scalable, Sanic is a next-generation Python framework and server tuned for high performance. This Sanic guide starts by helping you understand Sanic’s purpose, significance, and use cases. You’ll learn how to spot different issues when building web applications, and how to choose, create, and adapt the right solution to meet your requirements. As you progress, you’ll understand how to use listeners, middleware, and background tasks to customize your application. The book will also take you through real-world examples, so you will walk away with practical knowledge and not just code snippets. By the end of this web development book, you’ll have gained the knowledge you need to design, build, and deploy high-performance, scalable, and maintainable web applications with the Sanic framework.
Table of Contents (16 chapters)
1
Part 1:Getting Started with Sanic
4
Part 2:Hands-On Sanic
11
Part 3:Putting It All together

Summary

Now that we have learned how to manipulate both the request and the response, we can build some really powerful applications. Whether we are building an HTML-based website, a JSON-powered web API, a streaming content application, or a combination of them all, Sanic provides us with the tools we need.

One of the first things we discussed is that Sanic tries hard to not obstruct the build of an application. We, as developers, have the freedom to build with different tools and layer them together to build a truly unique platform. This is very much prevalent when we realize the freedom given to the developer regarding the response object. Do you need to write bytes directly? Sure. Do you want to use a specific templating engine? Not a problem!

Now that we have a basic understanding of how to handle the life cycle of an HTTP connection from a request through to a response, we can start to see what else we have at our disposal. In the next chapter, we will take a deeper dive...