Hacker News Reader

I have the exact same views.

In one of the discussion on building the structure, I was amazed to find that people do not think in terms of API.

As for me, I have always thought of having 3 different layers/servers independent of each other. Front-end, Back-end and Database

View on HN

It may be that we mean slightly different things here. I am not talking so much about the software architecture, but about the fact that the API between "front-end" and "back-end" should be the public interface. That does require a certain software architecture, though, of course ...

Just build your private API as a public API. That's what we've been doing and so far its turning out great

Yes ... But if the software arch does not decouple the front-end and back-end, then there are essentially no APIs.

An API approach is the best approach. Later it can always be opened to public.

Reply on news.ycombinator.com