Re^3: Architecture design for full stack development.

in reply to Re^2: Architecture design for full stack development.
in thread Architecture design for full stack development.

Thanks for the follow up on why you need an ORM.

If you're concerned about an attacker then take steps to harden your system (not just the database). If you're concerned about running out of values for a sequence then you should consider non-integer approaches; one such approach would be UUIDs.

Comment on Re^3: Architecture design for full stack development.

Replies are listed 'Best First'.
Re^4: Architecture design for full stack development. by erix (Prior) on Jun 28, 2017 at 09:44 UTC
... you should consider non-integer approaches; one such approach would be UUIDs. Possible, but then you might hit this: biginteger-vs-uuid inserts (image) There are ways to avoid that but let's wait till the OP gets a site up, and reaches, say, 10 tps. It may never happen, 'beginners'* often have unrealistically high hopes for their unborn brainchild. Well-trodden paths are boring, and often safest. *) Obviously, 'beginner' here in the sense of beginning a system (as OP says: 'a website from scratch')	[reply]

Replies are listed 'Best First'.

Re^4: Architecture design for full stack development.
by erix (Prior) on Jun 28, 2017 at 09:44 UTC

... you should consider non-integer approaches; one such approach would be UUIDs.

Possible, but then you might hit this:

biginteger-vs-uuid inserts (image)

There are ways to avoid that but let's wait till the OP gets a site up, and reaches, say, 10 tps. It may never happen, 'beginners'* often have unrealistically high hopes for their unborn brainchild.

Well-trodden paths are boring, and often safest.

*) Obviously, 'beginner' here in the sense of beginning a system (as OP says: 'a website from scratch')

[reply]

In Section Seekers of Perl Wisdom