DECISION NODE

Controlling the flow and rate of the traffic is known as Rate Limiting. Not having rate limiting may lead to exploitation of systems and high downtime.

The infrastructure persistence layer introduces the notion of a generalized contract that multiple 3rd party services of the same type can implement, and it leverages the idea of dependency injection when instantiating a service object that can accommodate for swappable services.

The main problem with images is that they are large. This size introduces performance, cost, and security concerns that warrant a different architecture than the rest of the data being served by a typical web app.

‍

Enter stacked workflows—a pragmatic solution designed to offer a structured method to manage and integrate changes in a way that promotes making small, frequent PRs.

The DiCE principle states that you must manage Data, Code, and Environment for reliable results.

Servers are buckling under the weight of millions of eager players, and you need to scale up fast. Can you handle the surge without crashes or lag?

Over the years, normalization has been the bedrock of designing efficient, reliable databases. Normalization is no longer the be-all and end-all of database design.

Gone are the days when server architecture decisions were as simple as choosing between buying hardware or renting a server. Today, we're faced with lambdas, managed container services, virtual machines, Kubernetes, and more.

‍

The topic of authentication/authorization is one of those things that all engineers come in contact with at some point but quickly forget.

Just about any app will include one or more toolbars or menus that provide a UI for users to perform actions or change configuration.

Sharing code between multiple services can turn into a topic of contention in a project team. The larger the service footprint, greater the intensity of debate on how to share functionality between the various services.

‍

Our product is a big hit, but we're starting to hear from our happy users that they're unable to roll it out organization-wide because they need a different configuration of permissions than our model provides. What to do?

You've decided that it's time to employ a specialized search database or service such as Elasticsearch. This leaves you with an important question: how to get all of our data indexed and available for search?