Bookmarks with tag "architecture", page 2 of 5
Managing distributed transactions across multiple microservices is challenging. Two solutions, two-phase commits and the Saga pattern are explored.
TL;DR: When you are making a new application that requires persistent storage of data, like is the case for most web applications, your default choice should be Postgres
Context, Containers, Components, and Code
Process background jobs in Go.
Make your client-side apps load fast and provide a good user experience.
OpenTracing is a new, open standard for instrumenting applications and OSS packages for distributed tracing and monitoring. In this post we explore the features and capabilities of OpenTracing.
This article looks at what it takes to start building an e-commerce data model and supporting infrastructure on your own. It also explores alternatives.
Managed runners for Github Actions
Access data stored in an external PostgreSQL server
Events/notifications service
FEATURE STATE: Kubernetes v1.21 [stable] A CronJob creates Jobs on a repeating schedule. CronJob is meant for performing regular scheduled actions such as backups, report generation, and so on. One CronJob object is like one line of a crontab (cron table) file on a Unix system. It runs a job periodically on a given schedule, written in Cron format. CronJobs have limitations and idiosyncrasies. For example, in certain circumstances, a single CronJob can create multiple concurrent Jobs.
Background jobs in Go via Postgres
An open-source & self-hostable Heroku / Netlify / Vercel alternative.
This article will introduce you to Postgres, explain the alternatives, and walk you through an example use case of pub/sub and its solution.
French cloud provider
Get to know all 14 UML diagram types with the help of examples.