Catálogo de publicaciones - libros

In this chapter, we have shown you an enterprise application architecture that can be used to ensure scalable and robust applications. We have talked about patterns and demonstrated how web services fit into the suggested architecture. The internal structure of an enterprise application is of high importance, and therefore we’ve included a section on coding conventions that can be used in real projects. We also talked about general exception handling and memory management that can make enterprise applications even more robust.

Finally, we introduced you to two different content management systems and compared them to each other. The use of a content management system can boost the development time of a content-based enterprise application and give developers time to focus on the business-critical parts in the application, instead of spending time on the boring tasks that the content management system can handle for them.

In Chapter 9, we will implement an example application based on this architecture to show how it looks in reality. We think this is the best way for you to really learn how to use the enterprise application architecture we outlined in this chapter.

In this chapter we’ve covered some important issues when it comes to data storage and how SQL Server fits into a storage policy. You have also seen some tricks you can use to improve performance in your SQL Server systems.

The focus of the chapter has been SQL Server 2000 since that is the database server most of our customers use right now. We also shortly covered SQL Server 2005 just to show a few of the cool features coming, buts since it has not even reached Release Candidate status when writing this we will not get deeply into it here.

Now it is time to put everything you have seen in this book to work. The next chapter will cover the development of a new application, following the guidelines we have discussed so far.

This chapter has focused on Service Oriented Architecture and how this might differ from component-based applications. You have seen examples of services and how to use them. Implementing Service Orientation affects the whole company, not just the development of single applications. This means that it’s quite an effort to implement SOA in your business. But, we believe that the future benefits are so great that you should definitely take a closer look at this area.

In this chapter, we have given you a closer look at how Windows works. You have seen the architecture of Microsoft’s operating system and hopefully now have a better understanding of what goes on under the hood—enabling you to build better, more secure, and more scalable applications.

In this chapter, we have shown you an enterprise application architecture that can be used to ensure scalable and robust applications. We have talked about patterns and demonstrated how web services fit into the suggested architecture. The internal structure of an enterprise application is of high importance, and therefore we’ve included a section on coding conventions that can be used in real projects. We also talked about general exception handling and memory management that can make enterprise applications even more robust.

Finally, we introduced you to two different content management systems and compared them to each other. The use of a content management system can boost the development time of a content-based enterprise application and give developers time to focus on the business-critical parts in the application, instead of spending time on the boring tasks that the content management system can handle for them.

In Chapter 9, we will implement an example application based on this architecture to show how it looks in reality. We think this is the best way for you to really learn how to use the enterprise application architecture we outlined in this chapter.

What is the position of yield management in hotel business organisations? What is its potential? Is this totally achieved or is there still an unexpressed margin? And with what organisational form does yield management best develop its potential? Innovations regarding organisational structure and work organisation in hotels have placed in doubt the role and position which yield management currently holds in hotels. This paper analyses, first of all, the principal causes for the failure of yield management systems and then relates these to the organisational structures widespread in the tourism-hospitality business. In this way the characteristics of a mixed or traditional system are analysed, along with the role that yield management plays in it; we shall also analyse a more advanced form of organisation, that of organisational learning, and its ability to strengthen the role and function of yield management, to the point of reaching the most advanced organisational form, still rarely recognisable in practice, which is the learning organisation which manages to develop to the maximum the potential of yield management as a management technique and not merely a technique for the determination of prices and the optimisation of revenue. The paper ends with the formulation of four different scenarios for the evolution of yield management and for their applicability.

This chapter has focused on Service Oriented Architecture and how this might differ from component-based applications. You have seen examples of services and how to use them. Implementing Service Orientation affects the whole company, not just the development of single applications. This means that it’s quite an effort to implement SOA in your business. But, we believe that the future benefits are so great that you should definitely take a closer look at this area.

In this chapter, we have shown you an enterprise application architecture that can be used to ensure scalable and robust applications. We have talked about patterns and demonstrated how web services fit into the suggested architecture. The internal structure of an enterprise application is of high importance, and therefore we’ve included a section on coding conventions that can be used in real projects. We also talked about general exception handling and memory management that can make enterprise applications even more robust.

Finally, we introduced you to two different content management systems and compared them to each other. The use of a content management system can boost the development time of a content-based enterprise application and give developers time to focus on the business-critical parts in the application, instead of spending time on the boring tasks that the content management system can handle for them.

In Chapter 9, we will implement an example application based on this architecture to show how it looks in reality. We think this is the best way for you to really learn how to use the enterprise application architecture we outlined in this chapter.

In this chapter we’ve covered some important issues when it comes to data storage and how SQL Server fits into a storage policy. You have also seen some tricks you can use to improve performance in your SQL Server systems.

The focus of the chapter has been SQL Server 2000 since that is the database server most of our customers use right now. We also shortly covered SQL Server 2005 just to show a few of the cool features coming, buts since it has not even reached Release Candidate status when writing this we will not get deeply into it here.

Now it is time to put everything you have seen in this book to work. The next chapter will cover the development of a new application, following the guidelines we have discussed so far.

In this chapter we’ve covered some important issues when it comes to data storage and how SQL Server fits into a storage policy. You have also seen some tricks you can use to improve performance in your SQL Server systems.

The focus of the chapter has been SQL Server 2000 since that is the database server most of our customers use right now. We also shortly covered SQL Server 2005 just to show a few of the cool features coming, buts since it has not even reached Release Candidate status when writing this we will not get deeply into it here.

Now it is time to put everything you have seen in this book to work. The next chapter will cover the development of a new application, following the guidelines we have discussed so far.