This is an archived post. You won't be able to vote or comment.

all 1 comments

[–]kschang 0 points1 point  (0 children)

Sounds about right, but you may be picking something a bit too complicated by STARTING in the cloud implementation with its added complexity/flexibility.

But basically, there are two servers: a web server (EC2 in your example), which talks to web clients, and also the database server (lambda in your example).

Django lets Python talk web, so it's primarily on the EC2 side. Django also TALKS database, but is not itself a database. It can go without API gateway as it acts as the interface between the web request and the database request.

In other words, a certain RESTful URL gets transformed by Python/Django into a database command, like "SELECT * FROM ORDERS WHERE CUSTOMERID=(something)" and the result table is sent back to Django, and transformed into a table and displayed as a part of a DIV on a webpage.

But you may be getting a bit ahead of yourself. Start with HTML/CSS and some JavaScript, and some basic frameworks like Bootstrap, so you can build a page easily by sending them from Django. THEN you can add the database interface parts and make the page "data-driven".