Summary of From SOA to SAAS
by Matthew Anders
TARGET AUDIENCE
The target audience are people that are technically inclined and are interested in finding new topics that may expand upon their current knoweldge base. In addition to this the target audience is individuals that are interested in learning about SAAS
TYPE OF DOCUMENT
This is an overview document talking about SOA and SAAS and what makes them distinct topics as well as a brief understanding of how they could be deployed
SUMMARY OF ARTICLE
This article starts off by discussing SOA and what it is and what the benefits are that SOA has brought to the market place. From here the author goes on to talk about SAAS and what that is and how it can be used. After these topics have been introduced the author then takes these topics further by talking about how they can be combined together. The article at this point finishes by talking about how a developer would design for a system like this and then also how a system like this could be created in the best way using the best of the software that exists today.
CONCLUSION
The most important take away from me was how these technologies can be combined to create something that works better than either one of them by themselves. I would not recommend this article to others because although it was interesting article it seemed to be fairly biased by the author and could have an impact on the decision make as to what technology to use and what tools should be purchased to support it. I gained a better understanding of what can be accomplished by combining these two technologies together to produce a final product that is better than its parts with this technology.
Summary #4
Summary of Distributed computing in JavaScript
by Matthew Anders
TARGET AUDIENCE
The target audience are people that are technically inclined and are interested in finding new topics that may expand upon their current knoweldge base.
TYPE OF DOCUMENT
This is a summary article of a new emerging technology being doing distributed computing using javascript in a web browser.
SUMMARY OF ARTICLE
The article starts off by introducing itself within the broader context distributed computing that the aurthor assumes the reader is familiar with. From here the author presents a very brief overview why doing distributed computing using javascript is important and why it could be usefull for people in the future. The author finishes by talking about the remaining challenges in distributed computing that still exist even with this new technology.
CONCLUSION
The most important take away from this article is the very fact that someone has discovered a way to do distributed computing using javascript through a browser window. I would recommend this article to other people that are trying to stay up to speed in advances in technology without needing to have a great in depth understanding of what those changes are. I gained a better understanding of what is possible to be done in the distributed systems and made me more aware of some new possible abuses that could take place when a view opens a web page.
Summary #3
Summary of Parallelizing Legacy code using Fine Grained Distributed Processing
by Matthew Anders
TARGET AUDIENCE
The target of the article is decision makers who are trying to find a
way to take a current legacy system and turn it into a distributed
system or modify it to take advantage of multiprocessors on a system.
TYPE OF DOCUMENT
This is a technical summary of a way to solve this technical issue for existing legacy software.
SUMMARY OF ARTICLE
This article starts out by talking about the general problem that
currently exists with legacy systems. From here the author starts to
talk about how there are many operators that run a legacy system that
wish they could turn their system into a distributed system for one
reason or another. From this point the author talks about the
difficulties associated with scaling a legacy system into a distributed
system due to the need to have thread safety and the need to be able to
access common memory which is not always possible in distributed
systems. The author then starts to discuss how you can go about trying
to find the parts of a legacy system that can be distributed and
parallized. The author finishes the article by talking about a specific
approach and technology that can be used in order to run the
distributed code in a way that would allow each thread to talk to
another and then the performance impacts of this approach.
CONCLUSION
I think the most important take a way from this article is the
discussion of the overhead that the author makes when the system is set
up on a distributed system. This shows the drawbacks of doing this to a
system and provides a very brief starting point to look at to figure
out if your specific system is worth distributing and if it would
actually provide benefit or if it would slow down the system in doing
this. This is huge since if it is not going to improve performance a
lot of times a business would not see the benefit of going through with
this. I would recommend this article to other system engineers and
software engineers that are currently going through a decision process
trying to decide if they should distribute a legacy application that
they are in charge of. The insight that I got from this article is just
how significant the drawbacks can be in distributing a serial process
if the proper analysis is not done up front.
Summary #1
Summary of Performance of Digital Pheromones for Swarming Vehicle Control
by Matthew Anders
TARGET AUDIENCE
The target of this article is individuals that have a computer science background but are interested in learning about what the current state of swarming project is specifically a project created for the US military.
TYPE OF DOCUMENT
This is a summary document of the current state of a project for the military on using swarming for their needs.
SUMMARY OF ARTICLE
This article started off by stating what the problems the authors were trying solve are. In this case these included surveillence, target tracking and targe acquisition. The author then presented an basic overveiw of what generic framework for swarm systems was by talking about the agents involved and the Pheromones that they used. From this point the authors then prceeded to talk about the various algorithms that they used to compute how fast these spread and disapate. The authors of the system point their theory into practice and present data on how their algorithms faired on each of their goals and provided the analysis that in some cases they performed well and in others it had struggled. The aritle is the finished up by discussing an actual demo that they presented to demonstrate how a system like this could behave in real life.
CONCLUSION
I think the most important thing that the authors of this article prodided is the definition of the algorithms that they used in this project. I would recommend this article to others that are interested in getting a good introduction into how AI can be created through a swarming methodology. I would also recommend this to people that are interested in trying to learn more about the state of swarming technology. I gained an understanding of how distributed communication takes place within a swarm.
Summary of What is SOA? - Increased Intrinsic Interoperability
Summary #1
From Daniel D. Messina
by Matthew Anders
Target Audience:
The tthe people that would get the most from this article are people with no or very limited understanding of what SOA is and what the benefits of it are. The target audience are the decision makers looking to use SOA.
Type of Document:
This is a very basic summary article. This could be looked at as a sales article for SOA as an overall concept.
Summary of Video
This article is concerned with the concept of different groups being able to utalize each other's software products with the least amount of pain possible. The talks about the goal of SOA in doing this is by increasing the interopability of products produced and thereby reducing the amount of integration that is needed. The article finishes by talking about how this can be achieved in SOA by having full adoption in groups of the standards that are in place.
Conclusion
The most important thing that I learned from this article is SOA is promoting the use of standards to promote interopability for products produced which is the same approach used time and time again and met with limited sucess due to limited by in to the standards. No I would not recommend this article to any one else. Most of the people that I know in industry have more than a basic understanding of SOA and as such this would be an article that is to high level to do them any good. The insight that I gained fromthis article is the fact that according to this article SOA is relying on the buy in of developers producing SOA products to be sucessful which can be difficult in the best of time due to the fact that SOA holds no influence over what these developers do.