Book Image

Cloud Native Python

By : Manish Sethi
Book Image

Cloud Native Python

By: Manish Sethi

Overview of this book

Businesses today are evolving so rapidly that having their own infrastructure to support their expansion is not feasible. As a result, they have been resorting to the elasticity of the cloud to provide a platform to build and deploy their highly scalable applications. This book will be the one stop for you to learn all about building cloud-native architectures in Python. It will begin by introducing you to cloud-native architecture and will help break it down for you. Then you’ll learn how to build microservices in Python using REST APIs in an event driven approach and you will build the web layer. Next, you’ll learn about Interacting data services and building Web views with React, after which we will take a detailed look at application security and performance. Then, you’ll also learn how to Dockerize your services. And finally, you’ll learn how to deploy the application on the AWS and Azure platforms. We will end the book by discussing some concepts and techniques around troubleshooting problems that might occur with your applications after you’ve deployed them. This book will teach you how to craft applications that are built as small standard units, using all the proven best practices and avoiding the usual traps. It's a practical book: we're going to build everything using Python 3 and its amazing tooling ecosystem. The book will take you on a journey, the destination of which, is the creation of a complete Python application based on microservices over the cloud platform
Table of Contents (14 chapters)
Creating UIs to Scale with Flux

Understanding Event Sourcing

By simple definition, Event Sourcing is an architectural pattern which determines the state of an application by a sequence of events.

The best way to understand Event Sourcing is by using an analogy. One of the best examples would be online shopping, which is an event processing system. Somebody places an order, which gets registered in an order queue for a vendor ordering system. Then, this status is notified to the customer at different stages of the order being delivered.

All these events, which occur one after the other, form a sequence of events called an event stream, which should look something like the following diagram:

So, Event Sourcing takes consideration of events which happened in the past, and are recorded for processing based on certain transactions.

An ideal Event Sourcing system is based on the building blocks shown in the following...