Architecture

Some people will call it cron jobs, scheduled tasks, or batch jobs. Whatever you call it, it’s a process that runs periodically looking at the state of a database to determine some specific action to occur for the various records it finds. If you’ve dealt with this, you probably know it can be a nightmare, especially with failures. And of course, these usually run in the middle of the night, so get ready for a page! YouTube Check out my YouTube channel where I post all kinds of content that accompanies my posts including this video showing everything in this post. Reservation… Read More »Avoiding Batch Jobs by a message in the FUTURE

What is the sidecar pattern? Applications and services often have generic concerns such as health checks, configuration, metrics, as well as how they communicate with each other either directly or through messaging. Services usually implement these using libraries or SDKs to handle these concerns. How can you share these concerns across all these services so you’re not implementing them in every service? The sidecar pattern and ambassador pattern might be a good fit to solve this problem. YouTube Check out my YouTube channel where I post all kinds of content that accompanies my posts including this video showing everything in this post.… Read More »Sidecar Pattern for Abstracting Common Concerns

Logical boundaries aren’t physical boundaries. A service boundary can be a one-to-one mapping of logical boundary and physical boundary but they don’t have to be. A logical boundary can have many physical boundaries and a physical boundary can be composed of many components from many logical boundaries. Do we have microservices to thank for the idea that the physical, development, and logical views are the same? This introduces a pile of unneeded complexity related to deployment, versioning, and data duplication. YouTube Check out my YouTube channel where I post all kinds of content that accompanies my posts including this video showing everything… Read More »Microservices gets it WRONG defining Service Boundaries