What's next ?


2 min read

Table of contents

No heading

No headings in the article.

We saw how the creation process of the data modelling, entity generation, repository layer, API handler and the main function which is where everything is connected. This service is by no means production ready or perfect or overflowing with functionalities ๐Ÿฅฒ. The main goal is to highlight a bare bones implementation how rust plays a role in the traditional web development with a web framework and a ORM. The takeaways is that we now have a 100% typesafe service that when polished a bit more with good error handling and adjustments could be production grade without a sweat. I hope I shed some light on how Actix and SeaORM is working and are promising projects which could evolve to become more robust and adoptions would increase. I encourage you to read through the docs and continue on this and build out the rest of the APIs maybe ?

  1. Create Todo POST /todos/
  2. Update Todo PUT /todos/{id}
  3. Delete Todo DELETE /todos/{id}
  4. Complete Todo PATCH /todos/{id}/complete
  5. Find by name GET /todos/?name= ( Remember we have indexed our todo_name property in database ๐Ÿ˜‡ Try out the API performance when index is available and also after removal )

Thank you so much for reading until the end and the entire code for this series can be found here and if you would like to support me, you can buy me a coffee โ˜•๏ธhere. Thank you and have an awesome year ahead ! ๐Ÿ™Œ๐Ÿป

Did you find this article valuable?

Support Omprakash Sridharan by becoming a sponsor. Any amount is appreciated!