Never write a database, even if you want to, even if you think you should
1–10 of 56 posts
Re: Never write a database, even if you want to, even if you think you should
#2what does "writing a database" mean?
Re: Never write a database, even if you want to, even if you think you should
#3"Always write a database. Even if you don't want to, even if you think you shouldn't."
Sometimes, naivety is a good helper when it comes to learning - too much knowledge of the task ahead can be demotivating. No one was born a professional developer either, and only by encountering and considering problems as they occur can one truly understand why certain decisions were made in the past and stuck around. Also, many great projects started as hobby projects. And not all projects have to become fully functional, or correct, or ready for production.
Re: Never write a database, even if you want to, even if you think you should
#4what does "writing a database" mean?
Building/developing/creating a https://en.wikipedia.org/wiki/Database [management system].
Re: Never write a database, even if you want to, even if you think you should
#5what does "writing a database" mean?
Writing software to store data, with retrieval and querying APIs, not using any existing database system.
Re: Never write a database, even if you want to, even if you think you should
#6Once you understand a consensus algorithm like raft, you kinda of have no choice but to write a database.
Re: Never write a database, even if you want to, even if you think you should
#7I've always wanted to write a database
Re: Never write a database, even if you want to, even if you think you should
#8... unless you're a developer. Then go right ahead -- you'll learn a lot doing it, and become a better developer in the process.
Re: Never write a database, even if you want to, even if you think you should
#9"When working with large amounts of data, steal as many ideas from databases as you can"
They have a lot of really simple, good ideas that can make your life a lot easier. Attempting to work on data intensive applications without stealing ideas from databases can make your life much harder.
Re: Never write a database, even if you want to, even if you think you should
#10Don’t take Twitter advice… this post does nothing but discourage play and experimentation.