What is the procedure for designing a web service?

Question

Software design

1) I wrote what problems my software should solve.
2) From this I isolated the domain objects.
What to do next is not clear:
a) from (2) to design an interface or
b) from (2) to design a database schema or
c) from (2) to design an API (will be SPA)?
What is the order?
Can you briefly explain on the fingers?
Are there any good articles or books by recognized gurus on this subject (M.Fowler, R.Martin,...)? I'm interested in some brief introduction, which made it possible to understand exactly the basics (because the Talmud would rather confuse and move me away from practice).

Answer 1

Not a great expert in marketing, but you forgot to conduct a market analysis as the first point. If there is no demand, then there is no point in doing it, if this is how the business is planned. And from a technical point of view, the best option is to file an MVP.

Answer 2

MVP

Answer 3

Any web service, this is ultimately an interface to the database, or rather to the data that is stored in it. Therefore, at the beginning of the database structure, then api (i.e. methods for accessing data in the database), then the application itself, which will use these api methods. The application will be further divided into design (i.e. application layout) and SPA development

Answer 4

The ideal design scenario is to write tests first. Write API tests for example in Javascript + Node.js + Jasmine + Request. In tests, implement API requests in the most convenient way in your opinion. Wrote a test, you can implement the end corresponding API connection point. At the initial stage, you can not use the database at all, operate with data in memory, in arrays or hashes to speed up.