Rod Johnson SpringSource The Future Of Enterprise Java

2y ago
18 Views
2 Downloads
1.69 MB
47 Pages
Last View : 18d ago
Last Download : 3m ago
Upload by : Albert Barnett
Transcription

Rod Johnson SpringSourceThe Future of Enterprise JavaKeynote, JAX (Wiesbaden), April 22, 2008

DOES ENTERPRISE JAVA HAVE AFUTURE?Speaker Company

Does enterprise Java have afuture?Ruby on Rails killed off enterprise JavaNo one still builds web applications usingJava todayNo one will date a Java programmerRod Johnson SpringSource

The facts don’t bear out the hype The Java market is not shrinking It is many times larger than the Ruby marketRod Johnson SpringSource

It’s what you compare Legacy Java technology vs Ruby on Rails looksdepressing Measures what Java vendors are promotingRod Johnson SpringSource

It’s what you compare Growth Java technology vs Ruby on Rails lookspositive Measures what people are actually doingRod Johnson SpringSource

But let’s not get complacent Enterprise Java needs to change There are strong competitive threats, and it hasnot fully delivered on its promiseRod Johnson SpringSource

Topics Forces for change Current trends– Introduction to Java EE 6– The market scenario– Technology forces Six Predictions for the future– Two totally free bonus predictions

The Real Topics The Cold War MonicaLewinsky Monty PythonRod Johnson SpringSource

Why does enterprise Java need tochange? Productivity challenge Need for modularity to reduce bloatand improve maintainability New requirements– SOA– Web 2.0Rod Johnson SpringSource

Trends in Platform Middleware: Disruption is inSightThe popular Java Platform, Enterprise Edition(Java EE) and .NET platform middlewaretechnologies are increasingly inadequate to coverneeds for extensive scalability and performance,event-based programming styles, advancedservice-oriented architecture (SOA) and dynamicapplication developments.- Gartner Group, September 2007

The Productivity Challenge Ruby on Rails challenge– Demonstrates common sense productivity solutionssuch as practical code generation No great leaps forward in enterprise Javaproductivity since Spring/Hibernate– Only incremental improvements Java community tends to miss low hanging fruit– This needs to changeRod Johnson SpringSource

Baggage slows enterprise Javadown When J2EE was conceived, Bill Clinton wasPresident and Monica Lewinsky was in the news– There may be another President Clinton, buttechnology has moved onRod Johnson SpringSource

Baggage Systems accumulatebaggage over time Need a regular clean outRod Johnson SpringSource

Java EE 6: An attempt to cleanhouse The first radical rethink of the platform Set to be final late 2008 or early 2009 Starts cleaning up the baggageRod Johnson SpringSource

The Two Philosophies Behind EE6 Extensibility Profiles Read the proposal (JSR-316) forinformation from the sourceRod Johnson SpringSource

Extensibility It would not be appropriate for the Java EE platform to grow withoutbound to include all the interesting and useful technologies desiredby web and enterprise application developers. Instead, we believe itis desirable to enable more of these technologies to cleanly layer onor plug in to Java EE application servers. By adding moreextensibility points and more service provider interfaces, these othertechnologies can plug in to platform implementations cleanly andefficiently, and be just as easy to use for developers as thefacilities that are built into the platform– Java EE 6 JSR Summary: Java EE 6 aims to make it easy and more natural forframeworks to build on the platform, recognizing that this is a keystrength of the Java ecosystemRod Johnson SpringSource

Profiles Different sets of platform technologyfor different purposes Finer-grained TCKs to allow forcompatibility testing of subsets Three profilesRod Johnson SpringSource

Profile A – Minimal, Lightweight –Equivalent to Tomcat Servlet 3.0 JSP 2.2 JSR-45– Debugging API EL 1.2 JSTL 1.2 JSR-250– Common Annotations for Java PlatformRod Johnson SpringSource

Key element of Profile A: Servlet 3.0 Biggest change relates to extensibility API allowing programmatic registration ofresources at runtime without everythingbeing tied to web.xml Intended to make it easier for frameworksto integrate “natively” with Java EEplatformRod Johnson SpringSource

Profile B – Adds persistence andtwo(?) component modelsFrom Profile A Servlet 3.0JSP 2.2JSR-45EL 1.2JSTL 1.2JSR-250Additional technologies EJB 3.1 (Lite) JTA 1.1 JPA 2.0 JSF 2.0 Web Beans 1.0?Rod Johnson SpringSource

Profile B Still relatively lightweight Numerous question marks– EJB 3.1 “Lite” still not clearly defined Subset likely to be restricted to local session beans and EJB3.0 “simplified programming model” without backwardcompatibility Essentially @Resource and @Interceptors– Inclusion of Web Beans (JSR-299) still unclear Unclear how this new component model relates to EJBRod Johnson SpringSource

Profile C – “Full Platform”The whole enchiladaSpecifications What Java EE used to be Sorry, I can’t make the font areadable size, there’s toomuch baggage Servlet 3.0JSP 2.2JSR-45EL 1.2JSTL 1.2JSR-250JTA 1.1JSF 2.0 *Web Beans 1.0 *EJB 3.1JPA 2.0JSF 2.0JAX-RS 1.0Connectors 1.6JAX-WS 2.2JAXB 2.2JSR-109 1.2JSR-181 1.1JMS 1.1JAF 1.1JavaMail 1.4JSR-115JSR-196JSR-88 1.2JSR-77 1.1JAX-RPC1.1JAXR 1.0Rod Johnson SpringSource

Profile C “Old J2EE” In Cold War terms, the Titan nuclear missile ofenterprise Java Less and less relevant to today’s requirements– Prevents agility in implementations– Contributes to bloat affecting development andoperations Modularity of the profiles A and B more relevantto today’s problemsRod Johnson SpringSource

Java EE 6: Overall Significance Recognizes that the world has changed Standardizes the kinds of real-worldinfrastructure that people use, while giving abrand guarantee Breaks up the cosy franchises of licenseeswho have relied on their ability to implementirrelevant APIs as barriers to entry forcompetitorsRod Johnson SpringSource

Opposing forces: Modularity andMonopoly Java EE 6 promotes modularity– Opens up competition Old application server market consolidates moreand more, reducing competition– When Bill Clinton was president, there were as manyapplication server vendors as interns in the OvalOffice– Now just a handful– Oracle’s acquisition of BEA takes this to a new levelRod Johnson SpringSource

Two clear market leaders, with aclear third place WebLogic and WebSphere togetheraccount for 70% of the market JBoss maintains a strong market positionbut has lost momentum since Red Hatacquisition Glassfish (Sun) is a promising product butis a dark horse, far behind market leadersRod Johnson SpringSource

The two market leaders are part ofmuch bigger plays Oracle has an aggressive vertical play– Applications– Middleware– Database– Even attempting to get into the OS business IBM has a massive services business anda vast software portfolioRod Johnson SpringSource

The two market leaders are partof much bigger plays BEA was an independent middleware vendor,with Java middleware its key product– BEA needed to win on “best of breed”– Could only survive as a company if WebLogic wasoustandingly good Oracle and IBM view their Java middleware aspart of a Microsoft-like full-stack solution– Neither needs it to be outstandingly good to meet their goalsRod Johnson SpringSource

But how do we measure the market? Fortunately, the old measurements of the market are obsolete Tomcat has overtaken the supposed market leaders andcontinues to pull ahead in production usage as well as indevelopment More evidence of the gap between the official world andreality that is bound to close70605040Springframework.orgBZ Research3020100WASJBossWLSTomcatRod Johnson SpringSource

PREDICTIONSRod Johnson SpringSource

Six predictions1. Real competition will return to the application servermarket2. Tomorrow’s application server will be lightweight andmodular3. Tomorrow’s application server will not merely implementJCP specifications4. The market will address the gap between Tomcat andWebLogic/WebSphere5. The gap between application servers and ESBs will bebridged6. EJB will dieRod Johnson SpringSource

Prediction 1: Real competition will returnto the application server market One of two things will happen– Java EE will cease to relevant In which case the existing franchises will be lessrelevant, or– (More likely) Java EE 6 will rejuvenate JavaEE Most interest will be in Profiles (A) and (B) The existing “whole enchilada” franchise will beless importantRod Johnson SpringSource

Prediction 1a Economic value will become more aligned withwhat people actually use Example– While WebSphere use is static, the WebSpherefranchise returns IBM massive and growing revenue– A huge proportion of the IBM user base uses only atiny part of the product and actively does not want thesize and complexity Market forces will drive realignment\Rod Johnson SpringSource

Prediction 2: Tomorrow’s applicationserver will be lightweight and modular OSGi provides a technical basis With Java EE 6 even Java EE is becoming modular The tend toward “self-assemble” of parts such as Spring,Tomcat Hibernate and other open source projects showsthe success of this approach in practice Natural trend towards getting the stack supported out ofthe box rather than building yourselfRod Johnson SpringSource

Prediction 3: Tomorrow’s application serverwill not merely implement JCP specifications New sources of relevant specifications andde facto standards The diversity of sources of innovation is akey strength of the Java platformRod Johnson SpringSource

Enterprise Java is no longer a oneparty state Not just the Party (the JCP) OASIS– SCA– Web Services standards OSGi Alliance– Dynamic modularization standards– More enterprise standards Open source projects– Eclipse Foundation is flexing its muscle on the server side

The JCP must look at wider world and accept that it doesn’t needto reinvent everythingJCP technologyIgnored existingtechnologyNegative consequencesand all other ORM Two complete failures (EJB 1.x and 2.x) HistoryTopLinkoffailurewhenthishasnotsolutions ORM inJava losesat least6 years Billions of dollars of wasted development effort fromhappenedcustomersEntity beansjava.util.loggingLog4JAdded complexity of pointless abstraction layerssuch as Commons LoggingEJB (DI)Spring, PicoContainer,HivemindLimited DI functionality in EJB 3 specification missesopportunity to match best practiceEJB3 (interception)Spring, AOP Alliance,AspectJ, AspectWerkzLack of knowledge of AOP in the expert groupproduces fragile, clunky API missing central AOPconceptsJSR 277(modularization)OSGi Ignoring input and experience from OSGi May split JCP as many organizations are deeplycommitted to OSGi

Signs of progress Recent signs suggest that the JCP isbecoming more open– Likelihood of an accommodation of JSR 277and JSR 294 and OSGi– JCP Chair Patrick Curran is committed tolistening to the community and increasedopennessRod Johnson SpringSource

Prediction 3a Within 18 months, the JCP will change tobe run through open source Sun is becoming an open source company– MySQL acquisition spells the end of theSoviet era of the JCPRod Johnson SpringSource

Prediction 4: The market will address the gapbetween Tomcat and WebLogic/WebSphere Currently the product division is an API division– A full-blown EE server with many APIs, many of which are notrelevant, plus open source libraries– A servlet engine plus the same libraries There is also a division on QoS and operations– WebLogic and WebSphere still lead here– Useful features for data center rollout There is a demand for a manageable, scalableproduct without the API baggage– So far, has not been a focus of open source projectsRod Johnson SpringSource

Prediction 5: The gap between applicationservers and ESBs will be bridged Old stovepipe architectural model is nolonger relevant SOA is spreading across enterprises The same modular infrastructure shouldbe able to support different architecturalscenarios– BEA’s mSA initiative (now probably on hold)was an interesting recognition of thisRod Johnson SpringSource

Today’s requirements drive need for consistentinfrastructure solution Monolithic J2EE onceserver seen as runtimefor everything Reality is more like this Distinct requirements needdistinct infrastructure But it should be based oncommon OAWeb appsWeb appsMOM

Prediction 6: The Black Knight willbe defeated It isn’t just a flesh woundRod Johnson SpringSource

EJB is dying Partly a reflection ofPrediction 5 – EJB was tied to aparticular architecturalscenarios Technical argumentsagainst EJB have longbeen clear Evidence in the market isnow also clear EJB is the Cobol ofenterprise Java– Declining in parallelRod Johnson SpringSource

Why does it matter? EJB is the centerpiece of “old J2EE” It’s vital that it is put aside for progress tobe made No amount of reinvention is enoughRod Johnson SpringSource

Conclusion We’re in for a period of rapid change Java EE 6 may keep Java EE relevant, butJava EE no longer shapes the future One of the key technologies that willshape the future is OSGi– Try to catch OSGi sessions at JAX It will be an exciting timeRod Johnson SpringSource

JAX-RS 1.0 Connectors 1.6 JAX-WS 2.2 JAXB 2.2 JSR-109 1.2 JSR-181 1.1 JMS 1.1 JAF 1.1 JavaMail 1.4 JSR-115 JSR-196 JSR-88 1.2 JSR-77 1.1 JAX

Related Documents:

May 02, 2018 · D. Program Evaluation ͟The organization has provided a description of the framework for how each program will be evaluated. The framework should include all the elements below: ͟The evaluation methods are cost-effective for the organization ͟Quantitative and qualitative data is being collected (at Basics tier, data collection must have begun)

Silat is a combative art of self-defense and survival rooted from Matay archipelago. It was traced at thé early of Langkasuka Kingdom (2nd century CE) till thé reign of Melaka (Malaysia) Sultanate era (13th century). Silat has now evolved to become part of social culture and tradition with thé appearance of a fine physical and spiritual .

On an exceptional basis, Member States may request UNESCO to provide thé candidates with access to thé platform so they can complète thé form by themselves. Thèse requests must be addressed to esd rize unesco. or by 15 A ril 2021 UNESCO will provide thé nomineewith accessto thé platform via their émail address.

̶The leading indicator of employee engagement is based on the quality of the relationship between employee and supervisor Empower your managers! ̶Help them understand the impact on the organization ̶Share important changes, plan options, tasks, and deadlines ̶Provide key messages and talking points ̶Prepare them to answer employee questions

Dr. Sunita Bharatwal** Dr. Pawan Garga*** Abstract Customer satisfaction is derived from thè functionalities and values, a product or Service can provide. The current study aims to segregate thè dimensions of ordine Service quality and gather insights on its impact on web shopping. The trends of purchases have

Jan 10, 2012 · Private Pilot Handbook Machado www.rodmachado.com Rod Machado 5. Rod Machado Rod Rod Machado 6. lift weight thrust drag 1-1 Rod Machado 7 B A C D. Rod Machado 8. 65 1-2 Rod Machado 9 A B. 1-3 . Private Pilot Handbook 2002 Library and Help 30% 100 Cessna 172 Rod Machado 35. Cessna 172 74 3-4 85 74 74 75 75 13 3-5 5 5 10 15 20 13 Rod Machado 36 .

Chính Văn.- Còn đức Thế tôn thì tuệ giác cực kỳ trong sạch 8: hiện hành bất nhị 9, đạt đến vô tướng 10, đứng vào chỗ đứng của các đức Thế tôn 11, thể hiện tính bình đẳng của các Ngài, đến chỗ không còn chướng ngại 12, giáo pháp không thể khuynh đảo, tâm thức không bị cản trở, cái được

Johnson Evinrude Outboard 65hp 3cyl Full Service Repair Manual 1973.pdf Lizzie Johnson , Reporter Lizzie Johnson is an enterprise and investigative reporter at The San Francisco Chronicle. Lizzie Johnson By Lizzie Johnson Elizabeth Johnson By Elizabeth Johnson Allen Johnson , Staff Writer Allen Johnson is a San Francisco Chronicle staff writer .