Java Stack 4

14
Java Stack 4 Providing Robust Back-end Web Services For Your Solution

description

Java Stack 4. Providing Robust Back-end Web Services For Your Solution. The Business of Providing Solutions. Portfolios provide a related set of solutions Each solution provides one more related services Web applications provide the ability to scale services across the globe. - PowerPoint PPT Presentation

Transcript of Java Stack 4

Page 1: Java Stack 4

Java Stack 4Providing Robust Back-end Web Services

For Your Solution

Page 2: Java Stack 4

The Business of Providing Solutions

• Portfolios provide a related set of solutions

• Each solution provides one more related services

• Web applications provide the ability to scale services across the globe

Page 3: Java Stack 4

Anatomy of a Solution

• The front-end• Delivered to the user’s device• Visible to end users• Provides customer interaction

• The back-end• Resides on the network• Invisible to end users• Provides the logic of the business’ core services• Performs the heavy lifting

Page 4: Java Stack 4

The Ideal Solution Portfolio

• Front-end applications• Light-weight• Loosely-coupled to back-end services

• Back-end application services• One-to-one relationship to the business’ core services (no duplication)• Consumable by multiple front-end applications (scalable)• Consumable by other back-end services (composable)

Page 5: Java Stack 4

The Life of a Solution

• Core business services remain fairly constant

• Slow evolution over time

• Customer expectations change often and quickly

• Rapid evolution over time

Page 6: Java Stack 4

Challenges: The Back-end

Application services often get tailored to a specific consumer, or front-end representation.

• Back-end becomes tightly coupled to the front-end

• Services must be re-written or re-factored for each front-end consumer

• Services become out-of-date when the front-end is out-of-date

Page 7: Java Stack 4

Challenges: The Front-end

Tightly coupled back-ends result in server-generated front-ends:• Frequent trips to the server• Less responsive user-interaction• Every view on the service must be secured• As many as 10x to 100x the number of resources than the actual number of

services that require the security• Complex security rules• Lots of room for error

Page 8: Java Stack 4

The Goal

• Extend the life of back-end services

• Allow front-end representations to:

• Evolve independently

• Be more responsive

• Be more secure

Page 9: Java Stack 4

Introducing Java Stack 4

• Repositioned solidly to provide robust, back-end application services• The recommended Stack for all ICS back-end services• Cloud-ready out of the box• Built upon the latest technological innovations of the global Java

community (Java 8, Spring Boot, etc.)• Simpler, cleaner, and more powerful than ever before

Page 10: Java Stack 4

Cloud / Platform as a Service

Browser / Mobile Device

Back-End(On the Server)

Front End(On the Client)

Front-end Applications

Static Content

Java Stack 4Application

LDAP

WAM

Other WebService

MLU WS

Oracle DB

Rest APICalls

Page 11: Java Stack 4

Java Stack 4 – Saving Time and Cost

• Provides a fully decoupled back-end service stack• Faster, easier development, testing, and deployment• Maximum scalability• Longer life• Much lower cost of maintenance

• Allows front-end solutions to maximum responsiveness• Reduces trips to the server• Allows front-ends to query only what has changed

• Easily secured• Finite number of service entry points

Page 12: Java Stack 4

Why Use Java Stack 4?

• The best guarantee for:

• Security – clean, declarative security model

• Efficiency – streamlined processes for development, testing, and deployment

• Scalability – consumable across many platforms and applications

• Repeatability – simple, well-understood patterns

• Supportability – familiar standards, reduced training requirements

Page 13: Java Stack 4

Making the most of Java Stack 4

1. Identify your core business services2. Federate each business service into a back-end service application3. Keep each back-end service tightly focused to its problem domain4. Keep each service generically consumable5. Compose your services within the front-end or within another back-

end, aggregating service

Page 14: Java Stack 4

Where to go from here?

• SORT 2014• Java Stack 4 RESTful Web Applications• Java Stack 4 with Spring Boot

• Java Stack 4 Documentation