Back End (Server Side)

Functions such as the inner workings, which might include business logic, updates, and changes are all the jobs of the back-end services.

Users don’t usually see what goes on at the back end, but they make everything work. Functions such as the inner workings, which might include business logic, updates, and changes are all the jobs of the back-end services.

The back end would store the data you collect from your users through the front end such as phone numbers, email addresses, and logs of IP addresses or credit card numbers. SQL or NoSQL databases store, retrieve, and back up your data.

API calls are used to connect different layers and clusters together that help your back-end process requests and communicate with other layers. Load balancers can be used for optimizing the user experience or connection layers for forming secure connections with the internet are all part of the back-end infrastructure.

A cloud-native tech stack will include multiple servers, containers running different applications, caches, web proxies, and databases.

You can find the sample backend code below to create a user record on our MySQL database.

from flask import Flask, render_template, request
from passlib.hash import sha256_crypt
import mysql.connector as mariadb
app = Flask(__name__)
db_connection = db.connect(user='chooseAUserName', password='chooseAPassword', database='Login')
@app.route('/')
def index():
  username = "newUserName"
  password = sha256_crypt.encrypt("newPassword")
  email = "[e-mail]"
  cur = db_connection.cursor()
  cur.execute('INSERT INTO Login (username, password, email) VALUES (%s, %s, %s)', (username, password, email))
  db_connection.commit()
  cur.close()
  return "New user added"
if __name__ == '__main__':
  app.run(debug=True, host='0.0.0.0', port='5000')t

Best Practices

Communication between your web application's front end and back end is what drives your web application. And this communication often goes over the internet unencrypted, as the software in use is often built without encryption in mind. Data should always be encrypted in transit between servers, as well as in storage — both at the API and database level.

So let's say you are using AWS S3 buckets to store files. You might develop a custom AWS Config rule to check that all objects stored in your S3 buckets are encrypted.

There should always be a secure backup plan. You should make sure data is backed up regularly and mirrored on several servers, in different physical locations or regions if possible.

Access to personal data should be limited to a few legitimate users. Precise permissions can be set at the API level, as well as for different users.

The session timeout system is tested and the token is invalidated after the user logs out. Limit API access should be limited to prevent automated attacks.

With multiple backends, services, and distributed servers a centralized logging system in which all services can write their log files is a good practice considering the complex back-end services of modern apps.

If you are using third-party code in your back-end, make sure you are using the latest updated versions of everything.