Prev threads (wtf):
>> 65933696
>> 65925151
>Free beginner resources to get started
Get a good understanding of HTML, CSS and JavaScript.
developer.mozilla.org
freecodecamp.com
codecademy.com
hackr.io
>Further resources
developer.mozilla.org
github.com
youtu.be
jsfiddle.net - Use this and post a link, if you need help with your HTML/CSS/JS
Planning to learn this stuff more seriously but just wanted to know:
Can you get by as a front end dev, or is it strongly reccomended to study full stack?
So many jobs demand google accounts now, I need to make a professional one instead of trap.lover666@gmail.com
>Can you get by as a front end dev, or is it strongly reccomended to study full stack?
They both exist but full stack devs can do both (plus back-end/API jobs) and front-end devs can only do front-end.
I'm building the server backend for a chat-like service. Which database solution should I use to store users, messages, etc.?
I don't need any complex queries, I just want it to be pretty fast in terms of reading/writing and be reliable.
I've never really used SQL for anything production-scale, I'm kinda scared of it as a whole. So I started with Redis. Don't feel completely comfortable with my choice, but it's pretty simple so I like it in that regard.
Are users/messages being stored a long period of time? Use a database like mysql/mongodb/postgres for that and not redis; redis is mostly for caching and 'forgettable' data in most cases.
Any of the databases I previously mentioned would be fine, although I think mongodb might be the easiest to grasp if you're new to stuff like this, and mongo would suit a node.js server (if that's what you're using). Redis would work as well, if your data doesn't need to be persistent, but I don't know how exactly your website wants to function, so I can't be more specific than that.
Also look into socket.io if you haven't already, it's perfect for chat services.
>Are users/messages being stored a long period of time?
Yes, at least users are. I thought about only keeping recent/undelivered messages in redis and maybe moving the rest over to colder storage like MySQL or something, but that would be pretty complicated for what it's worth.
While redis can be pretty persistent, I realize it's not its strong suit.
Do you happen to know how does the speed of inserting data in Postgres/MongoDB compare to redis? I want message inserting to be pretty fast (a message is just a string and some number fields like src id, dst id, time, etc.).
Also, the backend is Golang and Websockets. Pretty comfy so far, much better than Python (with asyncio), which feels like a mess in comparison.
I have a learning disability and would much rather work at my own pace than in a 'fast-paced' environment. Do webdev jobs exoist which generally take things nice and easy (i.e. not a team full of rockstar ninja developers working 12 hours a day with sprint meetings) or should I start my own business and market my skills even though I have no professional experience?
>pretty complicated for what it's worth
I don't know if I agree with that: learning and using MySql and etc. is a very good idea for resumes, 'serious' websites, and for becoming a more fully-fledged developer.
>Yes, at least users are
Permanently storing user info like usernames and passwords inside redis probably isn't a good idea.
There's also the whole logistics side of when/how to put your redis data into MySQL, and when/how to retrieve that data from either or both databases.
>Do you happen to know how does the speed of inserting data in Postgres/MongoDB compare to redis
Redis is much faster, speed is what redis was built for. I don't know the exact numbers off the top of my head though. Inserting data in either scenario wouldn't be too big of a deal though, the times will both be pretty fast for a low amount of inserts or retrievals.
>I have a learning disability
what's that?
Maybe look for remote jobs?