Manju

Greetings! GraphQL is rapidly gaining popularity as a more elegant solution for querying data compared to REST API. At the same time, NestJS streamlines the process of building efficient Node.js applications. In this article, I'll utilize two of them to construct a GraphQL server using NestJS. Note: I'll assume you have a basic understanding of GraphQL and NestJS. Source code -  Nest GraphQL GraphQL: A Quick Introduction GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. Schema: The GraphQL schema acts as a blueprint defining the data structure. It serves as the contract that establishes communication between the client and the server. Data Sources: These are the real data stores, which can be diverse, including databases, REST APIs, and more. Resolvers: Resolvers bridge the gap between the schema and data sources. They serve as the guides that tr...

Greetings! The Node.js ecosystem is undergoing rapid evolution, making it challenging to choose the right framework or library. The essential step is to build a solid foundation in basic JavaScript and Node.js concepts. But I'm curious about the newest trends in development hence trying NestJS. What is NestJS? Nest (NestJS) is a framework for building efficient, scalable Node.js server-side applications. Nest provides an out-of-the-box application architecture that allows developers and teams to create highly testable, scalable, loosely coupled, and easily maintainable applications. Why is it worth trying Nest shares similarities with Angular on the backend, drawing inspiration from Angular's concepts. For someone with a background in Java, like myself, it may feel reminiscent of working with the Spring framework. Getting started with Nest is straightforward and user-friendly. Apart from these points, there are some other aspects I'd like to emphasize. NestJS offe...

Greetings I was once tasked with setting up an earlier version of a database system for a demo. It took me a whole day to complete that task due to versioning issues in the required libraries. It was nothing but just pain. I lost valuable time as a developer that I can use for something more useful than struggling with setting up a database system. This is why cloud-based solutions are much better. AWS RDS provides us with many benefits over using traditional on-premises systems. OS upgrades and patching Automatic backups Replication High availability Security Multiple database options Hardware and networking So what is RDS? AWS RDS Amazon Relational Database Service (Amazon RDS) is a collection of managed services that makes it simple to set up, operate, and scale databases in the cloud. We can choose from seven popular engines. MySQL, MariaDB, PostgreSQL, Oracle, SQL Server, Aurora MySQL, and Aurora PostgreSQL. We can even deploy on-premises with RDS...

Greetings Emailing is a ubiquitous feature in modern applications that requires a reliable service to meet our email needs. Luckily, AWS Simple Email Service (SES) offers a cost-effective and secure solution. AWS Simple Email Service AWS SES is an email solution that relieves us of all operational responsibilities. It is an email platform that offers a convenient and affordable method for sending and receiving emails using your own email addresses and domains. Can I do "that"? When considering the use of such a service, we typically contemplate these functionalities. Personally, I experienced these aspects when incorporating AWS SES into our recent email feature. Sending simple emails Sending fancy HTML emails Send emails in bulk Send dynamic emails Store template somewhere Use list Use conditions Send attachments Send to multiple recipients Absolutely! SES indeed supports all of these features. Moreover, it can also be utilized for automatic...

Greetings In various software development scenarios, we inevitably encounter external dependencies, whether they are our own services or entirely third-party entities. Especially when it comes to microservices this is very common. Systems can fail or crash if we don’t plan and handle these scenarios properly. Having personally encountered such situations, I became increasingly curious to delve deeper into this. Note that there are no “exact” answers when comes to these kinds of situations. The best is to let the business decide which option to use as it will save a lot of time, engineering effort and of course money by not over-engineering. What can go wrong? Let's first categorize the scenarios that can happen when using external systems. Service Unavailable Service is not able to handle high load Service had implemented rate limits Service is slow All these will impact our businesses hence we need to carefully design our systems. However, we cannot say there is a perfect solution...