HTML5 28-Bar Chess development What is the development of the backend?

HTML5 28-Bar Chess Development (h5.ttkmwl.com) software applications are like icebergs. The user sees only part of the application-in most cases-the most part of the application is invisible. This is an elusive and mysterious "backend."

In the Web development chapter, we mainly discuss web development because it involves direct interaction with end users-what we can call "front-end Web development".

In most applications, the non-user interface code is much more than the user interface code. Complex systems are the logic that happens in the background to make them work.

We need to store and retrieve data, to follow business logic and rules, and to anticipate results. All this is happening behind the scenes.

The back-end developer is such a developer.

What exactly is back-end development?

The purpose of this article is that I will consider back-end development as a development that does not involve creating a build user interface. This may include back-end Web development, and may also involve writing APIs, creating libraries, or working with system components that do not have a user interface or even a scientific programming system.


In reality, even if front-end development gains much of the glory, most of the code that exists in the world (which can be said to be the most useful code) is back-end code that the end user never sees.

In short, back-end development is code that developers write that they can't see directly.

What does the back-end developer mainly do?

Depending on the size and scope of the application being processed, there is a big difference between what the back-end developer is going to do. When I was a back-end developer, I did a lot of work, working with business logic in the application, and extracting and retrieving data from the front end.

In the Web development world, most back-end developers engage in the actual logic behind building the applications they are working on.

Typically, front-end developers build the user interface, and the backend developers write code to make it work.

For example, a front-end developer creates an interface in the application with a button that presses a button to get the customer's data.

The backend developer writes code that makes the button work by pointing out what data is extracted from the database and passing it back to the front end (and finally showing up there).

Back-end developers may also be heavily involved in the system architecture, deciding how to organize the logic of the system so that it can be maintained and run properly.

He may be involved in building frameworks or system architectures to make it easier to write programs. Back-end developers spend more time implementing algorithms and solving problems than front-end developers.

I've always liked back-end development work because it's more like a challenge.

This is not to say that front-end developers do not solve the problem, but usually the front-end development work is more about creating the user interface and related content, rather than implementing the actual business logic to make the application work.


Front-end developers need to know a range of tools for creating user interfaces, and the backend developers typically use a completely different set of tools and skills to do their job efficiently.

One of the important skills that backend developers need is related to SQL and database. Most back-end systems need to connect to a database that stores application data.



Back-end developers typically work to write, read, and process data from a database or other data source, so having skills like SQL is important. Back-end developers-at least for web development-also need to be good at the server-side language of the technology stack they are using.

For example, while front-end Web developers are more focused on html,css and JavaScript, the backend developer needs to learn more about PHP Web frameworks, Ruby on rails,asp.net MVC, or any server-side web development framework that is being used to build applications. Featured Tutorials: Php from getting started to mastering self-paced tutorials

Finally, I would like to say that back-end developers need to learn more about the application architecture, because in most cases the backend developers need to build the architecture and internal design of the application.

A good backend developer has to know how to use various frameworks and libraries, how to integrate them into an application, and how to build code and business logic in a way that makes the system easier to maintain.

If you like designing an application's infrastructure, implementing algorithms and logic, and working with data, then you might like to be a backend developer.


In fact, full stack development includes all the components and layers of the processing system or software development stack. It may even involve understanding server hardware and architecture, or being considered devops.

Today, more and more software development positions are looking for developers who can do full-stack development because it is valuable for software developers to work on the entire technology stack involved, rather than two-way front-end development and back-end developers.

Part of the reason is that more and more applications now blur the boundaries between front-end and back-end development.

Many popular JavaScript frameworks, such as angular, allow you to create most of the content in the user Interface section of the system that can be considered business logic.

In addition, as more and more teams adopt agile approaches, individual programmers are required to not only work in their areas of specialization, because tasks are assigned to teams far more than individuals.

I think it's useful to be a full stack developer-and you should be fully aware of what's going on at every level of the software-but I don't think the "professional" full stack developer is the best idea because it's not a field of expertise.

Basically, you should focus on getting a broad knowledge of the most common technology stacks you might use, but you should choose one or two major majors and then really delve into the direction of your choice.

All software developers should know how to create a user interface, the basis of the framework used, how to store and retrieve data from the database in the application, and even understand how the infrastructure supports the software, and they do not need to be experts in all of these areas, because these areas are not only large but expanding.

Having all the knowledge that is common and effective in the technology stack, or specialized knowledge in some areas, may be much better.

Then, you can still call yourself "full stack", but in fact, for the team, your talent is much more useful.

HTML5 28-bar Board development What is the development of the back end?