No Clocks

This guide aims to introduce the reader to the main elements of the R ecosystem.

Collection of notifications, confirm dialogs and alerts for 'Shiny' applications - dreamRs/shinypop

Collections of resources for API Designers

Web applications can expose APIs so clients to interact with the application. Well-designed web APIs should support platform independence and service evolution.

If you’ve used the Plumber package to make R models or other code accessible to others via an API, sooner or later you will need to decide how to handle and report errors. By default, Plumber will catch R-level errors (like calls to stop()) and report them to users of your API as a JSON-encoded error message with HTTP status code 500 – also known as Internal Server Error. This might look something like the following from the command line: $ curl -v localhost:8000/ > GET /status HTTP/1.1 > Host: localhost:8000 > User-Agent: curl/7.64.0 > Accept: */* > < HTTP/1.1 500 Internal Server Error < Date: Sun, 24 Mar 2019 22:56:27 GMT < Content-Type: application/json < Date: Sun, 24 Mar 2019 10:56:27 PM GMT < Connection: close < Content-Length: 97 < * Closing connection 0 {"error":["500 - Internal server error"],"message":["Error: Missing required 'id' parameter.\n"]} There are two problems with this approach: first, it gives you almost zero control over how errors are reported to real users, and second, it’s badly behaved at the protocol level – HTTP status codes provide for much more granular and semantically meaningful error reporting. In my view, the key to overcoming these problems is treating errors as more than simply a message and adding additional context when they are emitted. This is sometimes called structured error handling, and although it has not been used much historically in R, this may be changing. As you’ll see, we can take advantage of R’s powerful condition system to implement rich error handling and reporting for Plumber APIs with relative ease.

Simple functions to lookup items in key-value pairs. See Mehta (2021) .

Learn how to use the open-source tool Plumber to create RESTful APIs for R programs.

Learn how to create a REST API in R using the plumber package.

CORS allows your web apps to use assets from other domains. Today, we explore CORS and learn to implement it in our own front-end projects.

A materialized view is a type of database object that contains any results derived from a query. Read on for a quick introduction.

Microservice architecture is one of the hottest software architecture trends these days, and it has forever changed the way we build enterprise applications. Here's all you need to know to get started!

In this Kubernetes Tutorial, you'll learn how to create a cluster, deploy, scale, and update your application.

Docker and Kubernetes have revolutionized the way we develop and deploy applications at scale. It's best to get started with them now.

Docker Compose is an advanced Docker tool that simplifies your workflow. In this article, we will show you how to get started with Docker Compose and its popular commands.

Having a good plan is the most important strategy for getting a project done. five steps to help you organize your work so you can sail through the project.