Backend Development

We’ve come a long way! We hope you are as excited as we are because this is the first chapter where we’ll write code.

  • PDF / 329,190 Bytes
  • 31 Pages / 504 x 720 pts Page_size
  • 72 Downloads / 240 Views

DOWNLOAD

REPORT


Backend Development We’ve come a long way! We hope you are as excited as we are because this is the first chapter where we’ll write code. In the previous chapter we discussed the design implementation of our product. You saw how everything developed from the concept phase, passing by the flow, mockups, and wireframes until its final visual stage: pixel perfect. In this chapter we are going to start our project by building our backend application that will support everything needed by the frontend application later. We will start by bootstrapping the project, so it can be built in a way we can later deploy. We will talk about data storage and ways of structuring an application and come up with a good architecture to minimize possible future inconveniences. Keep in mind that this chapter will introduce a lot of new terms, and we’ll provide several definitions and brief explanations, but it won’t dive into the details on any of them. The purpose is that in the end you get an idea on what you need in order to build a backend application and how these pieces work together. It will have some practical parts, but as you can imagine the project is considerably big, so we will just guide you through brief examples on how to bootstrap a project and some small implementation details, so you can get a feeling on how backend applications are built.

Note  If you are thinking about skipping this chapter because you are more into other topics, such as frontend, we invite you to think twice. We believe that even though you tend to lean more to one side of the development flow, it is important to have some knowledge on how things work together in general. Don’t worry, as we won’t get into much detail, but just all the steps needed to bootstrap a backend project and also considerations that we need to do when designing a backend application. We hope you are convinced now, and that you’ll stay tuned!

© Olga Filipova and Rui Vilão 2018 O. Filipova and R. Vilão, Software Development From A to Z, https://doi.org/10.1007/978-1-4842-3945-2_5

101

Chapter 5

Backend Development

About the Stack... We decided on the following stack because we felt that it is the one we can explain better and be more passionate about. We are not saying that this is the best stack—actually, we don’t believe that there’s a “best stack”; we believe there are a set of good stacks for what you want to do—some better than others depending on the nature of the project. There are several things that can help you decide what to choose, either because you are more comfortable with a specific programming language, or because there is one that you feel is better to solve a specific problem you have or just because you are somehow forced to use a specific stack since your company already invested before on it. We usually don’t engage in these kind of discussions, as they tend to lead us nowhere. We decided to write the backend application in Java 8. Why? Basically, because Rui has been working with Java for almost 15 years and he believes that it is a very nice langu