Similarities of Sequelize.js and Mongoose.js

pomyo — Fri, 16 Nov 2018 01:07:21 +0000

Choosing the right ORM to play nice with your database is important. It can save you tons of effort when trying to persist your data correctly and efficiently. With the emergence of NoSql databases like MongoDB, popular ORMs like Mongoose helps bridge the gap between your frontend and backend data while traditional relational databases like MySql make great use of Sequelize.

Although MySql and MongoDB are very different databases, the ORMs that support them by creating, finding, updating and deleting data are very similar if not the same.

Here are some ways they look the very similar.

For finding or selecting data, Mongoose and Sequelize both use .find() functions. To return everything in the table Mongoose uses .find({}) while Sequelize uses .findAll({}). To find by the primary key or the id, Mongoose uses .findById() and Sequelize uses .findByPk().

For creating documents or rows, Mongoose and Sequelize both uses the same .create() function to either generate new documents or add new rows to the table. Both have functions to send multiple inserts into their respective databases via .bulkWrite() for Mongoose and .bulkCreate() for Sequelize. Mongoose also have addition ways to create collections via .createCollection().

To update data, both ORMs provide a .update() function with a slight difference where Sequelize declares it's own .upsert() (insert instead if can't find anything to update) function while in Mongoose, an option can be specified on .update(). Mongoose in turn also have several variety of update functions like .updateMany() and .updateOne().

And finally, to delete things, Sequelize offer the mighty .destroy() function while Mongoose uses .delete()(originally also .destroy()). Mongoose can also .deleteOne() and .deleteMany().

What's first? Frontend or Backend?

pomyo — Tue, 13 Nov 2018 02:41:38 +0000

As a fresher straight out of college, I've never really grasp the differentiation between frontend and backend development. I've barely digested the grueling computer science courses of my degree let alone understand the many stacks that make up the entire development process. As such, my first job was synonymous to trial by fire. I had to do everything from setting up a database, figuring out how to run a server, deciding the best design patterns to use and cultivate my inner aesthetic self just enough to make a decent looking page with CSS.

Fast forward three years.

Now I have a relatively good grasp of the development world. Although far from being considered a good coder, the technical terms and buzzwords no longer strike me as hieroglyphics from an alien magazine. Researching issues are no longer seems like an olympic chore. But one thing still itches me whenever I start a new project. Frontend or backend first? While this may not be a question for those that have specific roles on the team, knowing which to start first helps me tremendously in organizing my code. From experience, I've noticed the pros and con of doing each first.

Front end first
Pros - Better organization of your design vision.
Use front end elements to gradually map out backend functionality.
Faster gratification from not having to redeploy.
Have something to show at the end of the day.
It's more fun.

Cons - Clients think you're done.
Nothing works (yet).

Back end first
Pros - Tedious part is done.
Requirements are quickly fulfilled.

Cons - Have very little to show to client besides code.
May not get a lot of feedback so may incur more refactoring later.

DEV Community: pomyo

Similarities of Sequelize.js and Mongoose.js

What's first? Frontend or Backend?