Intechnica Technical Director Andy Still describes the process of using a cloud solution to extend on-premise applications to the cloud.

1. Extending On-Premise Applications to the cloud
Andrew Still
Technical Director

2. Intechnica: Digital Performance
• develop complex, business critical bespoke online systems
• engineer performance into existing systems and
• develop processes and approaches to manage performance effectively
Intechnica helps companies to:

3. Intechnica: Digital Performance
Cloud pedigree:
Cloud based tool for
creating on-demand
cloud testing
environments
Cloud based tool for
generating load for
performance tests
Run North West AWS
User Group

4. The Problem

5. Andy!
I want a mobile app!!!
I want it now!
I want it to be brilliant!!
But I don’t want it to interfere
with any of my current
systems in any way!!

6. OK!!
I’ll get straight on it!!

7. Well..... How am
I going to do
that then?

8. What’s the application?

9. Tight integration with
other key internal
systems
Large datasets and
legacy data structures
Umbraco CMS
integration
Oracle Database
.net 4 web forms
application
£1.5 bn transactions per
yearB2B Order Capture
System

10. Current System

11. Why AWS?
Why not just build this on the
current system?

12. Longer term ambition to
open areas of the system
to additional 3rd party uses
Separation from core,
business critical systems
Platform Stressed at
peak times

13. We’ll need to introduce an API on
this system and a whole new
platform for mobile...

14. Like This

15. How will the caching datastore
work?

16. I’ll just fire up an
RDS Oracle instance
and sync the data

17. That seems a bit old style....

18. All data arriving in Json
from API, shall we store
it in that format
Must be focussed on
fast data retrieval
All data will be read
only, why the relational
overhead?
Can’t we build this on a
smaller footprint
That’s a lot of data to
sync
Those are heavy queries
on the current system

19. What else does AWS have to offer?

20. Sql
ServerS3
MySql
RDS
Simple
DB
Elasti
Cache
Dynamo
DB
Oracle
RDS

21. What is needed?

22. Multiple dataset sizes
- very large - >65mb
- very small - <100kb
Fast data retrieval
Must proactively cache,
shouldn’t be triggered
by end user.
Must be persistent and
survive EC2 machine
crash

23. No one size fits all....

24. .... But this is the cloud so it doesn’t
need to.....

26. Proactive Caching?

28. Scheduler? On AWS?

29. If only I could just
use an Azure Worker
role...

30. ... wait a
minute... I
can!

31. A hybrid cloud!!!

32. Now just need to share business
logic across standard and mobile
systems...

33. At least that
will be easy.
Thanks to
Dependency
Injection

37. Now where shall I store mobile
application data?

38. Let’s use
DynamoDB

39. Why?

40. It’s new, I
want to play
with it.

41. And if the client asks?

42. Intechnica: Chose DynamoDb for Mobile app storage
Why
 Quick and easy to implement
 Very small chunks of data to store
 No issue around data integrity – don’t need full relational structure
 No complex querying required

43. Finished Solution

45. Web: www.intechnica.co.uk
Email: andy.still@intechnica.co.uk
Twitter: @andy_still / @intechnica
Blog: http://blog.intechnica.co.uk/author/andyintechnica/
Tel: 0845 6809679
Address: Fourways House, 57 Hilton Street, Manchester, M1 2EJ