Moving from backend to frontend?

Question

ASP.NET

Hello! Tell me how best to do it, I write in C #, Asp.net, recently I started to master frontend and I like these three components, but there are moments that I don’t really like - interaction with the database, and indeed all work with the database, think through the architecture applications (I’m not strong at all in this matter, I just adhere to common truths, separation into layers, etc.) in connection with this, such a question is whether it is worth switching purely to the frontend, I don’t want to part with asp, but whatever one may say, you need to you need to deal well with the database, but as I said earlier, I don’t like these moments at all and there’s no desire to understand them, help with advice !?

Answer 1

Working with the database today is well supported by a whole galaxy of all kinds of ORMs; you can even not know SQL: drag yourself entities with simple Linq queries and rejoice. And for many web applications, the logic of working with the database is reduced to simple CRUD, i.e. no furious storages and complex transactions do not have to be written. If you take EF Code First, then you don’t even need to create a database by hand. In general, I do not see a problem.
As for the design, then I will disappoint. A programmer who does not know how to design (at least at some level) is not a programmer, but a small coder (not much higher level than a typist secretary). And going to the front is not a panacea, because. the modern front is kilometers of scripts and all sorts of frameworks. Those. there, too, you will have to design, and a lot (sometimes worse than in the back - it depends on the specifics of the application).
If the business logic is completely unbearable to draw, then it remains to throw it on someone else. Someone else will do all the necessary services, work with the database and other data sources, and provide these services to you in the form of a library, WCF service, via REST, or something else. Well, you just have to draw a front on ASP.NET, twitching services in the right places. In principle, in large projects, such a division into front and back programmers is quite applicable and often justified.

Answer 2

You need to pull yourself together, look into the eyes of danger and deal with the DAL well. Otherwise, you can run away from problems for a very long time and never become a good professional.
Climbing to the front is probably only after you fully know the back and only with the goal of becoming a full stack. The motivation to go to the front should be a design bone, and not a fear of the backend.

Answer 3

I'm not strong at all in this matter.

Your question already has an answer. Now you have a problem, and you are looking for where to run away from it. If you were not interested in the backend, you would not have asked us. If you did try to figure out at least the issue of interaction with the base, you would not ask either.
If what you mentioned is a problem for you,
it's too early for you to say that you "write in asp.net". Of course, you may know the framework enough, but so far it is not a tool in your hands. Why? And who today needs a C# backend without a database? Distributed computing? Well, maybe, but there are only a few such projects. Massively, these are LOB applications, and everything starts with the database there.
Therefore, first finish what you have already started. Or just take a break if you are tired, judging by the number of questions from you, you have taken up the topic quite seriously. Actually, why such a rush? Need to find a job urgently?