Book Image

Hands-On Software Engineering with Python

By : Brian Allbee, Nimesh Verma
Book Image

Hands-On Software Engineering with Python

By: Brian Allbee, Nimesh Verma

Overview of this book

Software Engineering is about more than just writing code—it includes a host of soft skills that apply to almost any development effort, no matter what the language, development methodology, or scope of the project. Being a senior developer all but requires awareness of how those skills, along with their expected technical counterparts, mesh together through a project's life cycle. This book walks you through that discovery by going over the entire life cycle of a multi-tier system and its related software projects. You'll see what happens before any development takes place, and what impact the decisions and designs made at each step have on the development process. The development of the entire project, over the course of several iterations based on real-world Agile iterations, will be executed, sometimes starting from nothing, in one of the fastest growing languages in the world—Python. Application of practices in Python will be laid out, along with a number of Python-specific capabilities that are often overlooked. Finally, the book will implement a high-performance computing solution, from first principles through complete foundation.
Table of Contents (21 chapters)
Free Chapter
1
Programming versus Software Engineering

What is a service?

Services, at their most basic, are simply programs that run in the background on a computer. They typically wait for input from somewhere, perform some actions based on that input, and return data that, at a minimum, indicates that the actions that were undertaken either succeeded or failed. At the most basic level, the input might not even be something that is visible to a user; services that wait for network activities, monitor filesystems, or even just run on some sort of timer-controlled basis, are very common in many operating systems today.

Services should always be available, running continuously, for as long as the host machine is running; this has some implications for how they are written and implemented, as follows:

  • They have to be very fault-tolerant: a service that crashes and dies every time something unexpected happens, and has to be restarted...