concept architecture in category spring

appears as: architecture, rchitectures, Architecture, The architecture, n architecture, The architecture, rchitecture, Architectures
Spring Security in Action

This is an excerpt from Manning's book Spring Security in Action.

I can guess that if you opened this book, you work on Spring applications, and you are interested in securing them. Spring Security is most probably the best choice for your cases. It anyway became the de-facto choice in implementing the application-level security for Spring applications. Spring Security, however, doesn’t automatically secure your application. It’s not some kind of magic that guarantees a vulnerability-free app. Developers need to understand how to configure and customize Spring Security around the needs of the application. How to do this depends on many factors, from the functional requirements to the architecture.

Dependency Injection: Design Patterns Using Spring and Guice

This is an excerpt from Manning's book Dependency Injection: Design Patterns Using Spring and Guice.

In this chapter, we will look at an incarnation of each major idiom and explain when you should choose one over another and why. I provide several strong arguments in favor of constructor injection. However, I will show when setter injection is preferable and how to decide between the two. Understanding injection idioms and the nuances behind them is central to a good grasp of dependency injection and architecture in general. Let’s start with the two most common forms.

There are a few more exciting possibilities. The kind of scaling we’ve seen thus far, adding stronger hardware to individual layers of an application, is known as vertical scaling or tiering. You will often hear architectures referred to as an n-tiered or vertically tiered system. This kind of scaling has its advantages, but it can get expensive very quickly. And for very large amounts of traffic, it can even become untenable. An increasingly popular alternative system is known as horizontal scaling.

Horizontal scaling refers to an architecture that increases its processing capacity by the addition of any number of homogenous nodes, each capable of performing the same function as any other. Incoming traffic is evenly distributed across several of these worker machines from a few strong-load distributors. This kind of hardware is both cheap and easily replaceable. And as it turns out, it is extremely powerful when scaling to very large loads.

Figure 9.1. Best practices for the language, or architecture with DI?