PaaS landscape has changed in 2011 with the unveiling of PaaS solutions like OpenShift and Cloud Foundry. The earlier PaaS solutions for Java developers like Google App Engine had lot of restrictions like learning new paradigm of programming , fewer choices in terms of languages and frameworks, diluted support which made it difficult to port existing applications to Cloud. With OpenShift you can very easily port your existing application to cloud without learning anything new or changing your code. OpenShift is great because it not only provides you with the choices of programming language (Java, PHP, Python), frameworks (like Spring or JavaEE), databases (like MySQL or MongoDB) but it also gives you control over the underlying infrastructure. In this session I will show you how you can deploy a Spring MongoDB application to OpenShift Express. Then I will show you how to deploy the same application on auto-scalable, cluster-enabled PaaS, OpenShift Flex.

2. A Happy Cloud Friendly Java Developer with OpenShift Shekhar Gulati Xebia

5. Lets developer focus on his job i.e. to write code.

6. You develop “Cloud Aware “ applications from bottom up.

7. Automatic Scaling.

8. Improves developer productivity.

9. As a developer it gives you power to prototype and create application rapidly.

11. Pre 2011 Java Developer was Sad PaaS == Problem as a Service

13. Tied to particular environment.

14. Vendor lock-in (lack of cloud portability).

15. Deployment on public cloud only.

16. Need to change the mindset.

17. Diluted frameworks.

18. Fewer Options or Choices.

19. Things changed in 2011

22. Cloud Portability.

23. No Proprietary Software.

24. No Need to change your code or learn something new.

27. Command Line,Eclipse & Forge plugin

28. Jenkins Support

29. MySQL, PostgreSQL,and MongoDB

30. Client Tools for data stores

31. Runs on top of EC2 but free

32. Supports 5 applications per user.

33. Multi tenant

34. Shell Access.

36. Install client tools. RHC Ruby Gem ,Eclipse Plugin

37. Create Domain

38. Create Application

39. Deploy using GIT. Just do git push.

40. I have written Spring Roo OpenShift Express add-on

42. MongoDB datastore

43. Spring Roo

44. Jenkins Support.

46. Non invasive (POJO based)

48. Each document is heterogeneous, and may have completely unique structure compared to other documents.

49. Fast and horizontally scalable.

51. Table -> Collection

52. Row -> Document

54. Code generator – Spring based enterprise applications.

55. Use best of breed.

57. No negative performance impact

58. No memory overhead

59. No Roo deployment

61. Java Max Heap Memory and permgen limitations

62. 100 process which translates to 80 Java Threads.

63. Currently, I think it is good for rapid prototyping.

66. Web UI and Command Line(Not tried)

67. Runs on your dedicated EC2 instance.

68. JBoss, Apache Web Server and Tomcat, MySQL, Memcached, Membase, Infinispan, MRG Messaging and MongoDB

69. Supports shell access.

70. Configure Components, Auto-Scaling, Performance Monitoring, Log Management

71. Coolest – Cost Calculator (I think)

72. Demo 2 Getting Started with Flex

74. MongoDB datastore

75. Spring Roo

76. Already created application.

77. Demo 4 –MongoDB Replica Set Scaling MongoDB Reads

78. Demo 5 Managing Overload- Scalability

79. OpenShift Flex Monitoring Performance

81. It is very easy to deploy existing applications.

82. Developer have to only focus on writing code and new apps not raising tickets.

83. Try OpenShift. It is awesome.

85. Spring portfolio projects , Big Data, NoSQL, Cloud enthusiast.

86. Freelance Writer

87. [email_address]

88. Twitter handle : shekhargulati

89. Thanks for listening