Ask HN: Is “Liaison” a good name for an open source project?

Post by jart » Tue, Oct 20, 2020, 2:29 AM UTC

mvila wrote: post #9

jart wrote: post #7

Earlier quoted context omitted.

Ah thanks for clarifying. Generating schemas and APIs from @annotations / @decorators is a well established technique. How does that remove four layers from the tech stack?

In a nutshell: - The frontend is "inherited" from the backend so there is no need to build an API server and an API client. - The database is abstracted away by an ORM. - The user interface can be encapsulated into the domain model. If you are interested, you can read this article for more details: https://dev.to/mvila/full-stack-development-should-be-easier...

What sort of tech stack do you run in production?

Post by mvila » Tue, Oct 20, 2020, 4:55 AM UTC

jart wrote: post #11

mvila wrote: post #9

Earlier quoted context omitted.

In a nutshell: - The frontend is "inherited" from the backend so there is no need to build an API server and an API client. - The database is abstracted away by an ORM. - The user interface can be encapsulated into the domain model. If you are interested, you can read this article for more details: https://dev.to/mvila/full-stack-development-should-be-easier...

What sort of tech stack do you run in production?

Any Node.js environment can run the backend. As for the database, Liaison supports only MongoDB for now, but more databases are expected to be supported in the future.

Re: Ask HN: Is “Liaison” a good name for an open source project?

Re: Ask HN: Is “Liaison” a good name for an open source project?