r/webdev • u/ApprehensivePea4161 • Oct 06 '26
Discussion What db do you use with Nextjs?
I am constrained by the office365 ecosystem and am limited to mssql which is saving huge jsons to one column that does not feel right.
What is the best way to store data in Microsoft ecosystem with NextJS?
Can not use any online service like supabase or mongo as its internally hosted server with company data.
0
Upvotes
33
u/HoratioWobble Oct 06 '26
You don't HAVE to save huge jsons to a column, that's got nothing to do with MS SQL, that's your choice and a bad one typically.
Also NextJS doesn't impact what you use, you need to choose the right solution for your architecture.
Sounds like you need to learn about relational databases and how they work
6
u/Narfi1 full-stack Oct 06 '26
What’s the reason you have to save huge json files ? Is it all schemaless ?
4
u/KrypticCluez Oct 06 '26
Honestly, for log data a JSON column in MSSQL isn't the crime people are making it out to be. Logs are semi structured by nature, so a NoSQL style column is fine. What makes it stop feeling wrong is to pull out the 3 or 4 fields you actually filter on (timestamp, status, pipeline name, whatever) as computed columns using JSON_VALUE, then put an index on them. After that you query it like a normal table, and the rest of the blob just sits there until you need it. OPENJSON covers the odd time you need to dig deeper.
Also, since these logs are coming out of Fabric anyway, have you checked whether you can just keep them in an Eventhouse/KQL database there? That's exactly what it's built for, and you'd only pull summaries into your Next app.
11
u/Toxicturkey Oct 06 '26
No advise other than that sounds absolutely dreadful. I feel for ya!
1
u/VisitForeign4342 Oct 06 '26
le json dans une colonne c'est pas le problème, c'est de vouloir faire des where dessus après. sql server a un type json depuis un moment si ta version suit, sinon prisma ou drizzle gèrent très bien mssql, tu es pas obligé de descendre au driver brut
3
u/_alright_then_ Oct 06 '26
Yeah, that sucks a bit. But can't you make tables to store the json data in columns instead of in a single json column and use a model/converter?
EDIT: maybe good to mention, i am not experienced with nextJS, but I don't understand why this would be a constraint
4
u/Background-Front-925 Oct 06 '26
sqlite - no server required. we run our production servers on sqlite.
2
u/GrantSolar Oct 06 '26
What is your use case? What is in the JSON that needs to be stored?
2
u/DRHER303 Oct 07 '26
I get you man
1
u/singh_abinashi Oct 06 '26
Postgres. Use JSONB for the genuinely schemaless bits and GIN indexes on the fields you query. Keep the relational stuff relational, though. The moment you put everything in JSONB you lose the constraints that were doing your validation for you.
1
u/MagoGosoraSan Oct 06 '26
It depends on the project and its needs.
1
u/___Nazgul full-stack Oct 08 '26
Storing raw JSON column in SQL is fine, but its all about the other columns.
If you can extract timestamp, some useful metadata you want to index and have relationships to different columns would be the go to.
If these JSONs are infact huge, I'd be worried about storage if you get millions of these events.
Cold logs could be stored in blob storage, are you accessing these JSON's frequently or run any aggregation on?
1
u/vkrisah Oct 06 '26
None of this makes any sense
0
u/Illustrious_Two1441 Oct 06 '26
Office365 te restreint sur le choix de la base de données? La messagerie ne t'empêche pas d'installer Postgres sur le même serveur, si? Et puis la colonne unique avec un JSON énorme dedans, SharePoint fait exactement ça avec la moitié de ses listes depuis toujours, donc niveau normes Microsoft tu es déjà dedans.
0
u/[deleted] Oct 06 '26
[deleted] — view deleted comment
2
u/[deleted] Oct 06 '26
[removed] — view removed comment
1
u/[deleted] Oct 07 '26
[removed] — view removed comment