Think about your team while defining architectures: A case study

Think about your team while defining architectures: A case study
Reading Time: 6 minutes
  • Flexible scaling: The application’s capacity varies depending on the total number of requests, which eases the billing in a project like this.
  • High availability: The configuration allows the application to run in different availability zones to ensure high availability of the service.
  • No idle capacity: The application will have a lot of times where we have no users, so having no resources allocated to the application would profoundly reduce expenses.
  • Defining the “best” technologies for a project is relative: The term best is always close, and we may need to consider at least what’s the best for the project, the timeline, the client, and of course, for the TEAM.
  • There are no good or bad architectures, only suitable or unsuitable: In some projects, microservices could be crucial and ideal. But in other cases, having a monolithic app can be the right solution for the problem. Generally, it’s essential to determine your project’s exemplary architecture without preconceptions.
  • The architecture of a project should evolve: The architecture of a project should follow the principle of a plan, implementation, testing and improvement. As your requirements grow, the project’s architecture should evolve to meet the needs.
  • Documentation is vital: It’s essential to keep up-to-date documentation of at least project architecture, DB schema, how to configure the application, share features, and other important information that may ease the understanding of the project.
  • Automate as much as possible: It’s crucial to automate as many things as possible to ease the different tasks. Automating things like deployments, project setup, database updates, ticket notifications, code revisions, etc., is easy.
  • Try the serverless-first approach: Creating serverless applications requires a mindset change so the results can be achieved as in a server-oriented application. But definitely, there is no turnaround once in the serverless world. The benefits are more significant than the downsides, so it’s key to ensure learning it in the right way to be aligned with the tendency.