《Experts one-on-one J2EE design and development》读书笔记3 J2EE设计中的新的选择

限时加码!20+主流AI编程工具免费用 购周边加赠Coding Plan Lite,Claude Code、Cursor等即刻畅享,学习进阶更高效! 阅读详情
 
在J2EE1.2的规范中,EJB只有远程接口,没有其他的选择。在当时,RMI也是支持远程客户端的唯一的选择。但是到现在这个状况已经发生了变化:
1. 从EJB2.0开始,提供了本地接口。因此,和EJB发布在同一个JVM中的客户端可以调用EJB的本地接口。
2. Web Services的出现。
 
EJB2.0本地接口的引入很大主要是为了解决EJB1.1的实体Bean的性能的问题,但是本地接口的影响却是远远的超出了实体Bean。我们现在有了选择,可以使用EJB而不使用RMI。我们使用EJB的时候,很多的时候并不是为了支持远程的客户端,而是为了EJB使用的其他的EJB(或者说J2EE框架)提供的其他的服务,例如事务等。以前我们使用EJB的时候,就必须忍受远程接口带来的额外的开销。有了本地接口之后,这就不是必要的了。
 
       而Web Services的出现,则为我们开发分布式的应用程序提供了另外一种选择。
       有了本地接口和Web Services之后,我们可以使用EJB而不使用RMI,也可以支持远程客户端而不使用EJB。这样就为我们进行J2EE的设计提供了很大的自由。
 
Expert one-on-one J2EE design and development》学习笔记1——JavaEE常用架构设计 JavaEE开发中程序架构设计不仅会影响程序性能、复杂性,同时还影响到程序的可扩展性和可维护性,目前业界有规范的JavaEE架构设计被奉为经典,下面将按照是否分布式进行介绍。 非分布式架构: 1.Web应用搭配业务组件接口架构: 经典三层架构:用户接口层、业务逻辑层和持久化层。 优点: (1).架构简单,是最常用最简单的Web应用架构,但是如果涉及到事务或者多线程问题时,需要 阅读详情

相关推荐

Expert One-on-One J2EE Design and Development

 What is this book about? The results of using J2EE in practice are often disappointing: applications are often slow, unduly complex, and take too long to develop. Rod Johnson believes that the problem lies not in J2EE itself, but in that it is often used badly. Many J2EE publications advocate approaches that, while fine in theory, often fail in reality, or deliver no real business value. "Expert One-on-One: J2EE Design and Development" aims to demystify J2EE development. Using a practical focus, it shows how to use J2EE technologies to reduce, rather than increase, complexity. Rod draws on his experience of designing successful high-volume J2EE applications and salvaging failing projects, as well as intimate knowledge of the J2EE specifications, to offer a real-world, how-to guide on how you too can make J2EE work in practice. It will help you to solve common problems with J2EE and avoid the expensive mistakes often made in J2EE projects. It will guide you through the complexity of the J2EE services and APIs to enable you to build the simplest possible solution, on time and on budget. Rod takes a practical, pragmatic approach, questioning J2EE orthodoxy where it has failed to deliver results in practice and instead suggesting effective, proven approaches. What does this book cover? In this book, you will learn When to use a distributed architecture When and how to use EJB How to develop an efficient data access strategy How to design a clean and maintainable web interface How to design J2EE applications for performance Who is this book for? This book would be of value to most enterprise developers. Although some of the discussion (for example, on performance and scalability) would be most relevant to architects and lead developers, the practical focus would make it useful to anyone with some familiarity with J2EE. Because of the complete design-deployment coverage, a less advanced developer could work through the book along with a more introductory text, and successfully build and understand the sample application. This comprehensive coverage would also be useful to developers in smaller organisations, who might be called upon to fill several normally distinct roles. What is special about this book? Wondering what differentiates this book from others like it in the market? Take a look: It does not just discuss technology, but stress its practical application. The book is driven from the need to solve common tasks, rather than by the elements of J2EE. It discuss risks in J2EE development It takes the reader through the entire design, development and build process of a non-trivial application. This wouldn't be compressed into one or two chapters, like the Java Pet Store, but would be a realistic example comparable to the complexity of applications readers would need to build. At each point in the design, alternative choices would be discussed. This would be important both where there's a real problem with the obvious alternative, and where the obvious alternatives are perhaps equally valid. It emphasizes the use of OO design and design patterns in J2EE, without becoming a theoretical book ,高清文档 

J2EE 应用设计模式推荐(摘抄自Expert One-on-One J2EE Design and Development

OO Design Recommendations for J2EE Applications It's possible to design a J2EE application so badly that, even if it contains beautifully written Java code at an individual object level, it will stil...

xingshen100的专栏 1620

Expert_J2EE_Design_And_Development 英文版

Expert_J2EE_Design_And_Development 经典书籍,学习spring思想必备!!

【笔记】《Expert One on One J2EE Design And Development》笔记

博主:该书是Spring框架的起源,J2EE(JavaEE)圣经,重要性自不多言。注意:该书出版时间是2004年。仅需阅读自己关注的部分。 1. 三层结构(P27) C1 讨论J2EE的架构,分布式架构下是否必须使用EJB组件。我不甚关心此章。不过作者提到的三层结构与我的认识不同。 1. Enterprise Information System(EIS) Tier 有时也叫 Integ...

huanqing2010的专栏 1862

JAVA程序猿推荐看的15本书_错过了是你损失

2019独角兽企业重金招聘Python工程师标准>>> ...

weixin_33953249的博客 4721

Expert One-on-One J2EE Design and Development体会

读Spring Framework的文档时候不可避免的了解到Expert One-on-One J2EE Design and Development这本书神往已久,今天粗略的看了一些内容,没发现什么惊奇之处。特别是MVC那一章,如果看过struts的文档,看那个就会觉得很少新意。 先把introduction的体会写上,introduction里面还是介绍得不错的,否则也没什么人接着看了。;)I

Tim, a lovable eccentric 5231

Experts one-on-one J2EE design and development读书笔记2 是否应该采用分布式架构

        J2EE提供了对分布式的支持,能够将应用程序的不同的组件发布到不同的JVM中,无论这些JVM是在同一台服务器上还是在不同的服务器上。分布式的J2EE应用程序的基础是带有远程接口的EJB。       但是,这个支持带来了一个误解:J2EE应用程序就必须是分布式的。       很多人认为分布式的应用程序是提供健壮的、可扩展的应用程序的唯一方法。这个观点是有疑问的,我们同

afrag的专栏 1371

【笔记】《Expert One on One J2EE Design And Development without EJB》笔记

博主:中文版翻译的质量很高,熊节统筹翻译的。由于是扫描版PDF,直接上截图了。这本书应该是 Java Web 必读之书,以前都不晓得有这种书。害,学校也不教(本科TM的也就教个Java教程前5章),工作时也没大神带(野路子公司)。 说正题:书比较啰嗦,讲EJB能讲5章。这EJB小公司用不到,没有几个亿的投资额,怕是用不到这个技术,可直接略过。 1. 业务服务层 Spring老大哥教你重新认识...

huanqing2010的专栏 1775

JavaEE框架---Spring---入门

Spring开源框架 Spring在英语中含义是春天,对于Java EE开发者来说,Spring框架出现确实带来了一股全新的春天的气息。早在2002年,Rod Johson在其编著的《Expert one to one J2EE design and development》书中,对Java EE框架臃肿、低效、脱离现实的种种现状提出了很多质疑,并积极寻求探索革新之道。由他主导编写了interf...

whale blog 265

J2EE Development Frameworks 英文原文

J2EE Development Frameworks 英文原文

expert one-on-one j2ee design and development 英文版 pdf

expert one-on-one,一本讲述Spring MVC开发的经典书,英文版,带目录,你值得拥有

编码规范(摘抄自Expert One-on-One J2EE Design and Development

Coding Standards J2EE projects tend to be big projects. Big projects require teamwork, and teamwork depends on consistent programming practices. We know that more effort is spent on software maintena...

xingshen100的专栏 2256

Expert one-on-one J2EE Design and Development》指导

   最近本人在阅读《Expert one-on-one J2EE Design and Development》一书,作为一个读者,把其中一些本人觉得比较认可和觉得比较重要的一些作者的设计思想与总结的指导准则记录在此。 一、设计。要编程到接口不要编程到类。这分离了接口与它们的实现。为了获得更大的灵活性,将实例变量和方法参数声明为具有所需的最小具体类型。首选对象组合而非具体继承

jimmy_cheung_jc的专栏 1018

再见了SpringMVC!这个框架有点厉害,甚至干掉了Servlet!

# 前言 对 Java 开发者来说, Spring 发布 5.0 正式版,而新版 Spring 的一大特色,就是 Reactive Web 方案 Web Flux,这是用来替代 Spring Web MVC 的吗?或者,只是终于可以不再基于 Servlet 容器了? # 基于 Servlet 容器的 Web MVC 身为 Java 开发者,对于 Spring 框架并不陌生。它起源于 2002 年、Rod Johnson 著作《Expert One-on-One J2EE Design and Develop

程序员白楠楠的博客 598

Java 五大框架之间的对比

Spring 及其优点大部分项目都少不了spring的身影,为什么大家对他如此青睐,而且对他的追捧丝毫没有减退之势呢Spring是什么:Spring是一个轻量级的DI和AOP容器框架。说它轻量级有一大部分原因是相对与EJB的(虽然本人从没有接触过EJB的应用),重要的是,Spring是非侵入式的,基于spring开发的应用一般不依赖于spring的类。 DI:称作依赖注入(Dependency In

xiaojiang博客 3万+

Expert One-On-One J2EE Design and development读书笔记1 企业应用程序架构的目标

  企业应用程序架构的目标:一个好的J2EE应用程序应该实现以下的目标:1.       健壮性        对于健壮性,没有什么好说的,应该是一个基本的要求了。没有一个用户愿意接受不稳定的系统的。2.       满足性能需求        应用系统应该能够满足用户对于性能的合理的期望。3.       可扩展        由于Internet应用程序的特点,

afrag的专栏 2313

Agent 记忆系统难在取舍

很多 Agent Memory 方案看起来都差不多:分层记忆、向量召回、长期画像、少用 token。真正拉开差距的地方,不在这些名词,而在边界条件。TencentDB Agent Memory 值得拆,是因为它把这些判断写进了代码和 prompt。图:Agent 记忆工程取舍。

afjkdajs的博客 238
上一篇: 《Experts one-on-one J2EE design and development》读书笔记2 是否应该采用分布式架构
下一篇: Java SE 7 新特性之文件操作(1)
afrag
博客等级 码龄20年 5粉丝 15原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值