Designing a Cache System

Load balancing helps us scale horizontally across an ever-increasing number of servers, but caching will enable us to make vastly better use of the resources we already have. Caches can exist at all levels in architecture. A cache is like short-term memory which has a limited amount of space. The cache is typically faster than the original data source.

Screen Shot 2018-06-21 at 1.45.54 PM.png
A simple global Caching System

Let’s talk about different approaches first.

Continue reading “Designing a Cache System”

Advertisements

Microservices vs Monolithic Applications

A developing a server-side enterprise application. You must think of different clients:

  • Mobile devices and its browsers.
  • Native mobile applications.
  • Desktop devices and its browsers.
  • Exposing your APIs to 3rd parties.
  • Integrating with other applications.
  • Executing business logic, accessing a database or exchanging messages with different systems.
  • Returning a response.
  • Figuring out technology stacks.
  • Keeping things in your mind such as CAP theorem.
  • many more depends on the complexity!

It is very hard to define an architecture that supports as a set of loosely coupled, collaborating services using the Monolithic approach. Let’s imagine that you are building an e-commerce application that takes orders from customers, verifies inventory, and ships them. The application consists of several components including the StoreFrontUI, which implements the user interface, along with some backend services for checking credit, maintaining inventory and shipping orders. The application consists of a set of services.

Continue reading “Microservices vs Monolithic Applications”

RESTful API Best Practices

This post covers best practices for building HTTP and RESTful APIs. Let’s start with the terms that we will use mostly:

  • The resource is a information that can be a singleton or a collection. E.g. /companies, /company and /employees are resources. Collections are set of resources, e.g. /companies collection resource is the collection of /company resource. /Company resource is a singleton resource. A resource may contain sub-collections such as /companies/{company_id}/departments and it can be followed by a singleton resource, e.g. /companies/{company_id}/departments/{department_id}.
  • Operations such as patch, put, update, delete, and post can be performed on these resources.
  • URL (Uniform Resource Locator) is a path.

Continue reading “RESTful API Best Practices”