Operations | Monitoring | ITSM | DevOps | Cloud

NestJS is fast becoming the de facto framework for NodeJS projects. Unlike older frameworks, NestJS was built with TypeScript, which has become commonplace in the JavaScript community. Frameworks like NestJS seem to be preferred by teams that adopt TypeScript. NestJS supports building APIs in REST and GraphQL. The goal of this tutorial is to show how you can add unit and integration tests to a NestJS GraphQL project and automate the testing process with CircleCI.

Making an Open Source Software with sensitive data and dozens of external integrations is a real challenge, here are feedbacks and tradeoffs we've made.

At incident.io, we're acutely aware that we handle incredibly sensitive data on behalf of our customers. Moving fast and breaking things is all well and good, but keeping our customer data safe isn't something we can compromise on. We run incident.io as a multi-tenant application, which means we have a single database (and a single application).

I am a big proponent of cross-functional alignment, as I remnded our ELT at a recent off-site meeting. There’s a lot of buzz about FinOps bringing financial accountability to cloud spend by eliminating procurement siloes and implementing cross-functional best practices. As the CFO of a SaaS company, I fully support this practice. In fact, Virtana recently made some changes to our cloud infrastructure as part of our own evolution.

Cloud computing is the on-demand availability of computer system resources without direct active management by the user. Instead, the delivery of said resources is available over the internet, which has made cloud computing a popular digital service that various industries use to operate and manage work tasks. How cloud computing services are implemented, hosted and accessed by users is called cloud deployment. There are different types of deployments, each with defined advantages for users.

In August 2016, the United States government announced a new federal source-code policy, which mandates that at least 20% of custom source code developed by or for any agency of the federal government must be released as open-source software (OSS). The memo of this policy also states that the Federal Government spends more than $6 billion each year on software through more than 42,000 transactions. Obviously, this is a huge business for all open-source developers.

Congratulations, you’ve been tasked with moving your workload to somebody else’s building! The “cloud” is just that: someone else’s data center. But their data center is pretty impressive (so there’s that). And, yes, while there are a million options available to you in AWS and Azure…a plethora of IT goodies, most of us will not use any of those bells and whistles, at least initially. We have to get there first—your basic lift and shift.

Let’s say you are writing a shell script for a systems housekeeping task. Perhaps the script is uploading backups to a remote server, or it is cleaning up old data, or it is making a measurement and submitting it to a somebody else’s HTTP API. What is the least cumbersome way for the script to contact you in case of problems? Let’s say you want to be contacted via email – how to make it work?