Book Image

Hands-On Enterprise Application Development with Python

By : Saurabh Badhwar
Book Image

Hands-On Enterprise Application Development with Python

By: Saurabh Badhwar

Overview of this book

Dynamically typed languages like Python are continuously improving. With the addition of exciting new features and a wide selection of modern libraries and frameworks, Python has emerged as an ideal language for developing enterprise applications. Hands-On Enterprise Application Development with Python will show you how to build effective applications that are stable, secure, and easily scalable. The book is a detailed guide to building an end-to-end enterprise-grade application in Python. You will learn how to effectively implement Python features and design patterns that will positively impact your application lifecycle. The book also covers advanced concurrency techniques that will help you build a RESTful application with an optimized frontend. Given that security and stability are the foundation for an enterprise application, you’ll be trained on effective testing, performance analysis, and security practices, and understand how to embed them in your codebase during the initial phase. You’ll also be guided in how to move on from a monolithic architecture to one that is service oriented, leveraging microservices and serverless deployment techniques. By the end of the book, you will have become proficient at building efficient enterprise applications in Python.
Table of Contents (24 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Chapter 1


Answer 1

Concatenation of a byte type, which is an immutable type, and a str type isn't permissible in the Python 3 standard; any attempt to concatenate these two types will raise TypeError.

Answer 2

The type-hinting support introduced in Python 3 is only intended to provide greater clarity in documenting the methods and the parameters and doesn't enforce any standards on the operations.

Answer 3

Beyond the functional and nonfunctional requirements, a software requirements specification document also specifies other requirements, such as UI, performance, business, and market requirements.

Answer 4

The various kinds of requirements are categorized as follows:

  • Must-have requirements: These are requirements that must be present inside a system. If any are missing, their absence will affect a critical functionality in the system.
  • Should-have requirements: These are requirements that, if present, will enhance the functionality of the application.
  • Could-have requirements: These are requirements that are noncritical in nature. If they are missing, they won't have any impact on the application's functionality.
  • Requirements wish list: These are requirements that the stakeholders might want to see in future updates of the application.

 

Answer 5

Once the software requirements specification document has been generated, the next steps in the process include the design phase of the software. In the design phase, the structure of the software application is decided upon and decisions are made regarding the possible technology stacks that might be used to build the software.