Learn Elixir: Midterm Project Prep

Learn Elixir In 12 Weeks: https://learn-elixir.dev/

Solidify your knowledge with Learn Elixir thus far; Midterm Project Prep details the instructions and qualifications to submit a suitable first project for code review.


Transcript:
Hello and welcome to the midterm project for learn elixir. For our midterm project, we want to encapsulate four separate goals to make sure that we really solidify the knowledge that we learned in the first half of this course in order to solidify our knowledge. The goals that we have, are to encompass the areas of OTP, elixir, ecto, as well as Phoenix, so our project should be created to encapsulate all of these parts, which means that for elixir, it really just means creating an application. Since anything that we do in elixir encompasses that part. For OTP, that means building some sort of monitoring system or a femoral caching or some sort of system that needs to be updated consistently and access to it really quick speeds. For Phoenix and graphQL, it really means just building out a graphQL API server so that
we can serve up the responses for our API and for ecto it means persisting some sort of information that we display in Phoenix to our Postgres database for this midterm.
I don't want to discourage anyone from having their own creativity when creating this project. If you have a project that you really want to create or you have any ideas on or even want some help founding the ideas for your project, feel free to contact us [email protected] for this midterm project, you're completely free to create whatever you want as long as it gets approved by us. Your project must encapsulate the areas that we went over, so you have to make sure that your project is going to hit all the areas that we just talked about. However, if your project does hit those areas and you'd like to use it for the mid term, please contact us and we'll make sure that your project is approved and that we confirm that it hits all the areas that we're trying to encapsulate. However, if you don't want to create your own project and you want to do something a bit more on guidelines, there's an example application that we can create in order to checkmark all of the areas for solidifying our knowledge. If you are creating your own project, you can skip these next few slides. If not follow along and you'll learn about, the project we're going to create. For our example project, we're gonna create a payment system. This payment system will allow us to pay different users who will have their own wallets and can hold multiple currencies at the same time. Each user can choose which currencies they want to hold as well as which user they'd like to send payments to in order to make sure that the currency is accurate. When we're sending a current, when we're sending money from one user to another, we have to ensure that we're using the exact exchange rates that are currently up, so we're going to be using an API in order to pull the currency exchange rates from a server and use those when we're doing our calculations. Essentially for our database, we're going to have a user system with wallets, which walls we'll have currencies and those currencies will have values and that will allow us to have users within our system that we can send money from one user to another. We'll do all of this over graphQL and we'll also set up graphQL subscriptions for when the exchange rate changes as well as for the current wallet value of a user given all their currencies so you can specify one currency and get back the total value of all of the users, different currencies in that one value. Some of the rules of this project are that we must use a process based monitoring for our exchange rates so that we can monitor what our exchange rate will be and that it's accurate and alive. The amount of currencies that we support should be able to be set inside of the config folder so that we can set what currencies we want to support in our application when we're compiling it. All of our user interaction functionality such as sending money or even looking at a user's count for money and how much they have should be done over graphQL queries and mutations. Finally, we should have tests written for all of the parts that we write that are OTP related or graphQL related so that we can ensure we have a level of guarantees. With all this in mind, good luck on the midterm project, and if you're following for the example project, you'll have a document in the download sectionfor the assignment. Otherwise, I'll see you in the next module. After the midterm project.