Part 1: Expose the Application¶
The DemoBrews app is currently running in an on-prem data center (the lab’s UDF deployment).
About the App¶
The app is made up of multiple services.
Single Page Application (SPA)¶
The customer has built a single page application (SPA). A client’s browser or mobile app retrieves all relevant assets (javascript, css, html) during an initial page load.
API Service¶
The client’s SPA retrieves application content by interacting with the API service. This includes retrieving product images, product descriptions, shopping cart data, etc.
Database Service¶
The customer’s database site on-prem. The API service makes queries to the database in order to retrieve assets like product descriptions and shopping cart data.
In its current state, the app’s components are restricted to services running in the customer’s legacy data center. This makes the application hard to scale and makes consuming resources at other locations impossible.
Section Goals¶
The customer’s application is only available through their on-prem data center. In this step, we will publish the application through F5 Distributed Cloud Console so all web traffic comes through the F5 Distributed Cloud Global Network. This will help us prepare for future states of the project.
In this state we will configure the following F5 Distributed Cloud Console components:
2 x Origin Pools
HTTP Load Balancer
Terminology¶
- HTTP Load Balancer
F5 Distributed Cloud’s reverse proxy and HTTP load balancer concepts allow for flow control of application and API traffic between services, to the internet, and from clients on the internet. HTTP Load Balancers allow for steering decisions based on URI or other HTTP based criteria.
- Origin Pool
An origin pool is a mechanism to configure a set of application endpoints grouped together into a resource pool. These endpoints could be IP:port tuples within a give site or a service discovered by one of F5 Distributed Cloud’s many service discovery methods. These objects will be used the next step.
App Data Flow and Architecture¶
Clients will retrieve static content for the Single Page Application (SPA) from an HTTP load balancer (not pictured). The SPA will interact with an HTTP load balancer to retrieve application data from the API service. The API service queries the on-prem database.
The hosting assets are confined to the customer’s on-prem data center. The app will be exposed to the internet through the F5 Distributed Cloud Global Network.
Note
The AWS site you previously created is not yet used.
Contents: