4 ms·

I choked seeing how frontend was relegated to a single box at the end of the diagram, given that it's complexity often dwarfs the rest of the system. Most backe

I choked seeing how frontend was relegated to a single box at the end of the diagram, given that it's complexity often dwarfs the rest of the system. Most backends these days can be had out of the box by using something like Supabase, AppWrite, Firebase or tons of others. These days web app backends seem almost too trivial to bother.

danparsonson 3y ago
Did you mean complexity of deployment? What does a modern front-end need beyond something to serve up resources at a reasonable rate?
mhuffman 3y ago
In many cases a front end is just a view of some API call which can be much more than a db query. Some times it is the other way around where the the front end is just pulling data and all the business logic is done in the browser. So I guess it depends on your needs.
Etheryte 3y ago
Quoting the article makes it clear the author doesn't understand the problem space. "Just keep things as simple as possible" is not an architecture. > For the front end – use whatever technology your front end developers prefer. Just keep things as simple as possible.
- lucidguppy 3y ago
  Your correct I'm not super well versed on the front end. I was under the impression that a react app could be hosted on an s3 bucket with reasonable performance.
pc86 3y ago
There was a day not too long ago when the front end was a single box on a diagram. HTML forms posting to an API, then a redirect to a different page covered 99% of your front end. There are quite a few react nextjs etc etc apps that could benefit from being a little more on that end of the spectrum.
hobs 3y ago
A backend isn't just a database, it sounds like you've just made your frontend your backend as well.
radicalbyte 3y ago
What kind of systems do you work on? This might be true for a certain class of mobile apps / websites it is absolutely not true for significant systems. Just because your TODO app only needs a BLOB storage with OIDC for the backend does not mean that "all of the complexity is in the frontend". Pick a random Fortune-500 company. Their IT system complexity will be dominated by the "backend". Easily 90-99% of their complexity and budget will go into building and maintaining those systems.
evantbyrne 3y ago
That's quite the self-snitch. Even the most complex web applications don't need a separate frontend server, let alone multiple. The only exception would be having an app or something that can't just render HTML sent straight from the backend.

danparsonson 3y ago

Did you mean complexity of deployment? What does a modern front-end need beyond something to serve up resources at a reasonable rate?

mhuffman 3y ago

In many cases a front end is just a view of some API call which can be much more than a db query. Some times it is the other way around where the the front end is just pulling data and all the business logic is done in the browser. So I guess it depends on your needs.

Etheryte 3y ago

Quoting the article makes it clear the author doesn't understand the problem space. "Just keep things as simple as possible" is not an architecture. > For the front end – use whatever technology your front end developers prefer. Just keep things as simple as possible.

lucidguppy 3y ago
Your correct I'm not super well versed on the front end. I was under the impression that a react app could be hosted on an s3 bucket with reasonable performance.

pc86 3y ago

There was a day not too long ago when the front end was a single box on a diagram. HTML forms posting to an API, then a redirect to a different page covered 99% of your front end. There are quite a few react nextjs etc etc apps that could benefit from being a little more on that end of the spectrum.

hobs 3y ago

A backend isn't just a database, it sounds like you've just made your frontend your backend as well.

radicalbyte 3y ago

What kind of systems do you work on? This might be true for a certain class of mobile apps / websites it is absolutely not true for significant systems. Just because your TODO app only needs a BLOB storage with OIDC for the backend does not mean that "all of the complexity is in the frontend". Pick a random Fortune-500 company. Their IT system complexity will be dominated by the "backend". Easily 90-99% of their complexity and budget will go into building and maintaining those systems.

evantbyrne 3y ago

That's quite the self-snitch. Even the most complex web applications don't need a separate frontend server, let alone multiple. The only exception would be having an app or something that can't just render HTML sent straight from the backend.