Skip to main content

56 posts tagged with "serverless"

View All Tags

· 2 min read
Enes Akar

Recently, Netlify announced Edge Functions where you can run your code at edge locations on Deno runtime with globally low latency. In this post, we will build a simple app which runs Netlify Edge functions and accesses Upstash Redis as a data store. Upstash Redis is a perfect match for Netlify Edge Functions because:

  • Upstash Redis has Global database type where the Redis replicas are distributed all over the world. So your edge function will access to the closest region with low latency.
  • Upstash Redis has a built-in REST API and SDK which is free from any connection issues common in serverless runtimes.
  • Upstash Redis has a JS SDK which is built and tested with Deno runtime

· 2 min read
Enes Akar is a great platform where you can distribute your application globally. When your application is global, your data needs to be global. You can run regular Redis as a app but the problem is it is located in a single region. On the other hand, Upstash Redis Global Database perfectly fits as it is globally replicated. Moreover, thanks to its REST based SDK, it does not have any connection problem in stateless runtime.

In this article, I will create a basic Node.js application which accesses Upstash Redis and deploy it to platform.

· 4 min read
Andreas Thomas

What is keepalive?

Whenever you make an HTTP request to a server, your computer and the server create a connection, sending some data back and forth and closing the connection afterward. This is an excellent system, as it cleans up after itself if you infrequently connect to the same server. However, suppose you need to communicate with the same server multiple times in short succession. Then, every new connection would require a new TLS handshake, which causes numerous round trips between you and the server. So instead, we can keep the connection open and reduce the latency for each subsequent request by enabling keepalive.

· 7 min read
Kay Plößer

Delivering a project on time usually means you need to leverage as much existing technology as possible. Every decision you make that leads to a custom implementation must consider that you also need to maintain your own solution. This is why open-source tools like Strapi are the way to go for building the REST API for your next project.

Strapi is a state-of-the-art headless CMS. It allows you to define your schema with a graphical interface, so even non-technical people can model data. Your development team can focus on building web and mobile apps and delivering new features without worrying about the backend implementation. After all, a big open-source community maintains Strapi.

· 2 min read
Mehmet Dogan

Since our initial release last year, Upstash was compatible with Redis® API up to version 5. Our Redis offering was lacking commands such as GETDEL, LMOVE, COPY and features such as ACL which were introduced in Redis 6 (and 6.2).

Happy to announce that Upstash Redis databases are now compatible with Redis commands up to version 6.2.

· 5 min read
Omer Aytac

Tracking logs and errors in a software product is very essential for reliability and maintainability. Kafka is one of the most powerful solution for collecting/storing logs and activities. Use cases can be seen in this blog.

In this post, we will use Upstash Kafka to collect errors and logs occurred while users are using the mobile application which is built by React Native. Once the logs are stored in Kafka, there are endless possibilities how to consume them and integrate to log analysis tools.

· 13 min read
Burak Yılmaz

Sometimes it is the best to create reminders for your annual events so that you don't forget and miss those special dates.

If you and your team/friends are using Slack, then it is a good idea that you automate these reminders via slackbots.

While doing so, if you want your slackbot to be a low maintenance one in that; it may be the best to use serverless technologies for concurrent interactions with the source, also enabling horizontal scalability.