Database design is much slower than Java code development. If the database is designed and Java only develops interfaces, it will take more time to write 35 SQL statements. However, in order to ensure correctness, the code must be refactored beautifully, which requires a lot of This test takes time, and a week is not too much.
I’ve been writing stuff these days, and it took several days to write the front-end interface. It’s not easy to make the front-end good and beautiful, but Java uses Spring+SpringMVC+MyBatis and RESTful style to write the interface. The Java code only takes about 4 hours. , but database design and URL design take about 2 times as long as writing code.
Of course, it takes less time to write code in Java. The premise is that you are already familiar with building a server-side development environment in Java and have a set of templates. This requires a lot of accumulation. Basically, I just write the functional interface code directly. For me, environment construction is It doesn't take much time.
Conclusion: With so many interfaces, different people, different accumulations, there is no good measurement standard, and the implementation model has not been determined. For example, a stand-alone Web server can expose the URL, or use distributed services. For example, Dubbo’s exposed interface does not require a URL. Whether to use a cluster, whether permission control for interface access is required, how to manage permissions, how much data needs to be processed, whether distributed cache needs to be used to improve performance, whether the database needs to separate reading and writing, code management, etc. Code quality requirements, interface requirements, etc. If you want to achieve a high-quality implementation, even a month is not a long time. If you want to write a demo-level thing to show that I can develop quickly, it will not take 2 days to complete it. Yes, but what's the use?
What is hidden behind the interface is the complex thing, and writing the code for the interface is nothing. Maybe you use this question to measure the development time required for budgeting. If a good person delivers it in 2 days, should you only pay for 2 days?
In fact, various web frameworks in Java are quite mature. Unlike nodejs development, which has to consider issues such as scaffolding and deployment, Java already has good solutions
I have developed similar functions in node before. Starting from scratch (counting from the time of setting up the node, not working overtime) will only take more than half a month, and I am still half-assed at the backend
You may not be able to finish it in two months. It also depends on the interface requirements. Taobao’s registration is also an interface, and the registration of ordinary small sites is also an interface.
What’s the point of not having a database or a framework? Why does JAVA come up with TP again? It still solves the problem. . . Speed mainly depends on the maturity of the framework and database design, and also depends on the skill proficiency of the person writing the API. If these prerequisites are ready, it will be solved in a week or two. If not, it will take several months. .
It depends on the detailed design. There are several types of recommended products in the carousel on the homepage. Is your recommendation based on the flag of the product or is it a recommendation system? Should the recommendation system be connected to a big data provider or should it be done by itself based on purchase volume? What is the recommendation algorithm? These are not yet clear, so the workload cannot be assessed
. Development of an interface. If you want it to be quick... it is possible to write 10 in a day. If you want to write one in 4-5 days... it is also possible... There are many things that are not available Under certain circumstances... the workload cannot be evaluated!... Without a detailed PRD document for the product... everything is negotiable
PS: I’m a little doubtful... the poster is a product maker and doesn’t understand technology...
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Database design is much slower than Java code development. If the database is designed and Java only develops interfaces, it will take more time to write 35 SQL statements. However, in order to ensure correctness, the code must be refactored beautifully, which requires a lot of This test takes time, and a week is not too much.
I’ve been writing stuff these days, and it took several days to write the front-end interface. It’s not easy to make the front-end good and beautiful, but Java uses Spring+SpringMVC+MyBatis and RESTful style to write the interface. The Java code only takes about 4 hours. , but database design and URL design take about 2 times as long as writing code.
Of course, it takes less time to write code in Java. The premise is that you are already familiar with building a server-side development environment in Java and have a set of templates. This requires a lot of accumulation. Basically, I just write the functional interface code directly. For me, environment construction is It doesn't take much time.
Conclusion: With so many interfaces, different people, different accumulations, there is no good measurement standard, and the implementation model has not been determined. For example, a stand-alone Web server can expose the URL, or use distributed services. For example, Dubbo’s exposed interface does not require a URL. Whether to use a cluster, whether permission control for interface access is required, how to manage permissions, how much data needs to be processed, whether distributed cache needs to be used to improve performance, whether the database needs to separate reading and writing, code management, etc. Code quality requirements, interface requirements, etc. If you want to achieve a high-quality implementation, even a month is not a long time. If you want to write a demo-level thing to show that I can develop quickly, it will not take 2 days to complete it. Yes, but what's the use?
What is hidden behind the interface is the complex thing, and writing the code for the interface is nothing. Maybe you use this question to measure the development time required for budgeting. If a good person delivers it in 2 days, should you only pay for 2 days?
An answer from the front-end dog
In fact, various web frameworks in Java are quite mature. Unlike nodejs development, which has to consider issues such as scaffolding and deployment, Java already has good solutions
I have developed similar functions in node before. Starting from scratch (counting from the time of setting up the node, not working overtime) will only take more than half a month, and I am still half-assed at the backend
You may not be able to finish it in two months.
It also depends on the interface requirements.
Taobao’s registration is also an interface, and the registration of ordinary small sites is also an interface.
It depends on the specific requirements document. If the requirements are not high, writing four or five brainlessly a day should be about the same
What’s the point of not having a database or a framework? Why does JAVA come up with TP again? It still solves the problem. . .
Speed mainly depends on the maturity of the framework and database design, and also depends on the skill proficiency of the person writing the API. If these prerequisites are ready, it will be solved in a week or two. If not, it will take several months. .
A conservative estimate is about a month. The interface logic may be simple or complex, and the time required may vary. It cannot be generalized
It depends on the detailed design. There are several types of recommended products in the carousel on the homepage. Is your recommendation based on the flag of the product or is it a recommendation system? Should the recommendation system be connected to a big data provider or should it be done by itself based on purchase volume? What is the recommendation algorithm? These are not yet clear, so the workload cannot be assessed
.
Development of an interface. If you want it to be quick... it is possible to write 10 in a day. If you want to write one in 4-5 days... it is also possible...
There are many things that are not available Under certain circumstances... the workload cannot be evaluated!... Without a detailed PRD document for the product... everything is negotiable
PS: I’m a little doubtful... the poster is a product maker and doesn’t understand technology...
It’s nonsense to discuss workload before designing.