Skip to main content

Backend Developer & Development [ Part 2 ]

Incoming Requests

In incoming requests, you must know about HTTP verb / method, queries, params, headers, body and flows. 

For HTTP verb / method, there's are many but i only introduce most common one. All of the method have their own usage like
  • GET           -  For client GET data from server-side
  • POST         -  For client POST data at body to server-side for creation or other requests that used post body.
  • PUT            - For client replace specific data with body given.
  • PATCH       - For client update partial data with body given.
  • DELETE    - For client delete specific data from server-side.

For queries, params, headers and body, they like a message that from client. 4 of them will receive on different places.

  • Queries  - Can found at behind of the URL. Look like ?value=abc.
  • Params   - Defined by backend developer when routing. Look like 'sampleurl.com/:id' when pass 'sampleurl.com/123', id would be 123.
  • Headers - Using postman you will see some default headers like Content-Type, X-Response-Time and Content-Length. Most of the backend would implement these headers and for authorized usage also.
  • Body      - When method POST used most of the backend developer would pass data using post body. For now many of the framework have default used JSON as parser.
As incoming requests to processing requests, they would pass into middleware of the backend framework. Most of the time they will checking body is it JSON and authorized access. Once all the condition pass only will start processing requests. After processing data, it will response to client that i called it outgoing response.

Outgoing Response

In outgoing response, you must know headers, response and status. Response most of the time is same structure, cause only need to reply to client is it success or not, fail due to what and success with payload that client needs. Headers would be quite same with incoming requests, what different is on framework, some of the framework would add customized on it. Status would be a verb like HTTP method, it is a number that can defined many means.
  • 200+ - Success
  • 300+ - Redirection
  • 400+ - Client error
  • 500+ - Server error
In a short saying on these would be like that for more information you can look into https://developer.mozilla.org/en-US/docs/Web/HTTP/Status.

Processing Requests

There was a complete flow from incoming until outgoing. And another you need to know is type for processing requests, it can be sequential or parallel. 
  • Sequential  - mean only process one requests whatever how many requests has send to the server
  • Parallel       - mean process multiple requests at the same time
We will stop here, Next time will talk about framework features and how they work.

Popular posts from this blog

Preparing some plugins for upcoming server

Since i still having a free server from mine friends who in Taiwan keep supporting me for server hosting. For long time busy, and he hope i would still operate and having a survival server so i coming to build up a survival server that not like before only enhance survival gameplay instead of new gameplay and make player doesn't even know how to play. Here come with some idea before i preparing: Custom Building Structure ( Make player easier for some basic works ) Custom PvP & PvE Mechanic ( Make item flexible with skill system and update-able, also work with entity ) Socialize Gamplay ( Guilds & Friends & Party & Mail System ) Daily Gameplay ( Questing, Events )  Any suggestion would be appreciated ( welcome to inbox me :] ) Some images about mine developments in these 2 days. Mine Structure API Skill API work with Items system & Status system And here is the video about the Custom Building Structure Part. As past exp

Backend Developer & Development [ Part 1 ]

Backend developer is a develop who maintain the work users /  clients can't see such as processing transaction, data structure, data transfer. These works would contains in a API server and API server contains many endpoint that can call by anyone but only success when fulfill endpoint requirements so it is secured. API Server also know as REST API ( Representational State Transfer ). It's processing like client request to server & after server process return response to client. API Server is develop by backend developer and this api server can be many type and different language, different framework such as Ruby on Rails ( RoR ) using Ruby Python PHP ( Laravel & Yii2 ) Java ( Spring ) C# ( ASP.NET & NancyFX ) Node.JS ( ExpressJS, SailsJS, HapiJS, NestJS, FeatherJS ) Different framework have their own advantages and can be used on different projects based on their features and usage. In the development not only choosing frameworks also need to ch

A long journey before i going back to other platforms

That's a long journey for going work on mine other projects due to i participate a startup mate together work on a startup projects. In the projects, i learn and workaround back-end framework in many of languages ( due to private work cant show too much code ). Also i does self-taught some front-end frameworks by learn from mine front-end mate's code & re-base using flutter . It was taken about half of a year to build up a proper back-end server due to inexperienced of my skills and technique so take time to learn. I have also played around many frameworks such as   Back-end ExpressJS - Most basic of the back-end frameworks NestJS - A progressive Node.js framework for building efficient and scalable server-side applications on top of TypeScript & JavaScript (ES6, ES7, ES8) heavily inspired by Angular SailsJS - A MVC framework inspired from Ruby on Rails, have a really good structure and newbie friendly HapiJS - Quite same with Express but more exte