Developing Applications with MySQL and Java

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 121


Insert Picture HereDeveloping Applications with MySQL and JavaMark MatthewsConsulting Member, Technical Staff - Oracle


The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.


Graphic Section Divider


Please ask Questions!

● This is not a lecture – but an opportunity to learn from each other● The only assumption I'm making is that you're not expecting to write PHP● (if you haven't seen some of these frameworks, methods, etc. it's okay) e


Elements of Scalability

● Vertical Scalability – single component responding to load● Largely driven by efficient resource usage

● Horizontal Scalability – more components responding to load

● Architecture that allows “divide and conquer”


Designing for Scalability

● Vertical Scalability● Algorithms

● Persistence tuning

● Horizontal Scalability

● Partitioning by workload

● Partitioning by service


Architecture – Birth of an Application

UI

Business Logic

MySQL

Persistence


Architecture – Growing the Application

UI

Business Logic

Write

Persistence

Client APIs

3rd Party

Read


Architecture – Growing the Application Again

UI

Business Logic

Write

Persistence

Client APIs

3rd Party

Read

Caching



UI

Business Logic

Write

Persistence

Client APIs

3rd Party

Read

Caching



by-data A by-data B by-data C






Customers

Inventory/Rentals Comments/Rating


Design for Growth from the Start

● Separation of concerns from the start● Business Logic

● Natural place for units of work, partitioning

● Natural point to build APIs to deliver services

● Persistence Logic

● Easier to tune/fix persistence performance issues – once -

● Easy to cache if in one place


This Lab

● MySQL in a replication hierarchy● Managed by MySQL Sandbox

● “Sakila” Schema

● Simple harness over a layered service architecture

● Spring, Hibernate, EhCache

● Evolution

● Performance, Partitioning by workload, (further into cells)


Take Aways

● Design for scale up front● Demarcate units of work with transactions

● Makes it possible to load balance

● Natural cleave point for partitioning by service

● Compartmentalize persistence

● Fix performance issues once

● Add caching in one place

● Testability


Technology

Developing Applications with MySQL and Java