I've had to ask the question a hundred times to find an answer that made sense. If you're new to web development, you might be asking, "what's an API?" I will, however, provide a TL DR at the bottom if you just want to get the summary and key learnings. Your mileage may vary if those particulars are important to you! I should caveat that I won't be promoting one framework over another, and haven't yet compared things like deployment, authentication, or scalability. You can access the full code on GitHub, as well. In this article, I'll also provide code examples and the resources that I used to build everything. I thought my findings might prove useful to others out there who are researching back end frameworks for small projects. I began my development process with Express, which, for reasons I'll soon explain, led me to also check out Flask and ASP.NET. The natural starting point was to build a simple front end that would send requests to an API, which would in turn read from and write to a local database. There are a lot of back end framework options out there, and I'm most familiar with JavaScript, C#, and Python (in that order), which limited my options somewhat. ![]() The objective was straightforward: to build a simple RESTful API that would allow a front end app to perform basic CRUD operations, providing me with an introduction to what the development process would look like. I've been shopping around for a back end framework to support a tabletop game app, and decided to do some research to determine the best fit for my needs.
0 Comments
Leave a Reply. |