The SOA Magazine IV edition focuses on Industrial SOA articles which showcase that SOA is much more than a web service. Rolando Carrasco and Arturo Viveros showcase in their SOA Myth Busters article the evolution of the SOA Suite towards a complete platform over the last 10 years. An industrial SOA platform contains also API management to secure web services, as well b2b as a trading hub between external partners.
What is the use case for Business Process Management versus Services Oriented Architecture. SOA is mainly used for data mediation and process orchestration between different IT systems. BPM is focused on automation on human based processes like an employee holiday request. Key is to re-use the SOA web services for your BPM deployment. In our holiday request example we can re-use a web service from the HR system which informs the employee of the available holidays. In this magazine edition you learn on the BPM Side more about Gateways and how Link Consulting is using a generator to create Human tasks. Thanks to Mark Foster who highlights in his article 10 best practices for SOA Suite and BPM Suite a must read!
Adaptive Case Management is ultimately about allowing knowledge workers to work the way that they want to work and to provide them with the tools and information they need to do so effectively.
After seven months of traveling Curiosity lands on Mars. The engineers in NASA mission control are excited to start scientific research. These scientists have a special challenge; the Mars rover is so far away and the signal takes so long, that they need to rely on automation in order to maintain control in the wildest scenarios. There are many decisions that must be made on a daily, and even on a minute-to-minute basis. Involving the scientist in every possible decision, given the round trip time to consult and answer, would slow the research to – literally – a crawl.
The scientists who operate the rover are knowledge workers. Just like knowledge workers in a business setting, they must figure out how to accomplish goals, as they uncover new information that affects their goals. The automation that they use built into Curiosity is very much like the business processes that businesses use to achieve their goals: the process works fine as long as the situation matches what was expected. But what happens to a business process when confronted with something unexpected? This chapter takes us on an exploration of how to adapt to the unexpected--including a Little Green Man--using the Mars Curiosity as an entertaining, but highly enlightening example.
For more infomation please visit the Future Strategies bookstore here.
Authors: Thomas Erl,Clive Gee,Jürgen Kress,Berthold Maier,Hajo Normann,Pethuru Raj,Leo Shuster,Bernd Trops,Clemens Utschig-Utschig,Philip Wik,Torsten Winterberg
Innovative service technologies are becoming valuable assets for businesses that need to stay competitive in the face of increasing globalization and market complexity. While computer processing power is becoming faster and cheaper, search engines, instant messaging, and social media channels are generating floods of information that escalate demands for consumable and accessible data.
As the world's economies engage one another through offshoring, outsourcing, and supply chaining, localization is required to accommodate different currencies and languages. Globalization, recession, invention, and communication are some of the driving forces behind a next generation of technologies and practices that revolve around software programs designed in accordance with the paradigm of service-orientation. Such programs, referred to as "services," are expected to do more for less with greater efficiency in order to meet business challenges head-on.
We have reached a stage in the evolution of service-oriented computing where modern service technology innovation is building upon mature service platforms at the same time that proven delivery techniques and design patterns are building upon an established service-orientation paradigm. These developments have made it possible to create service-oriented solutions of unprecedented sophistication.
Cloud Computing Hype
Why is everyone talking about cloud computing? Drawn-out, expensive IT projects that are planned andimplemented without any benefits for the business stakeholders are commonplace. In contrast, cloud computing offers business users the chance to immediately implement services with usage-based billing that are tailored to their requirements, often without the need to consult with the ITdepartment. However, aspects like security, architecture, availability, and standards are often not evaluated. Cloud consumers find themselves at the mercy of the cloud provider. Scenarios that require changing cloud providersafter a cloud provider goes bankrupt, and the associated moving of data and/or applications, have not yet been sufficiently tested. Business continuity should play a key role from the start of a cloud evaluation process. One of the greatest challenges here is the integration of existing data and systems into the cloud solution. Without integration spanning between clouds and on-premise systems, processes can only be executed inisolation, leading to cloud-specific silos of isolated solutions. Important information for users is not available across processes and systems. Problems that would have occurred in the company’s internal IT are nowshifted to the cloud provider. To prevent “legacy clouds” or solutions that are hard to maintain, it is important to manage the entire architecture proactively and, in particular, the integration into the cloud. Even if cloudproviders want us to believe otherwise, not every aspect of IT can be outsourced to cloud solutions! Read the paper here.
Release: OTN & Service Technology Magazine 4.2013
Authors: Jürgen Kress, Berthold Maier, Hajo Normann, Danilo Schmiedel, Guido Schmutz, Bernd Trops, Clemens Utschig-Utschig und Torsten Winterberg
SOA and service-orientation have laid the foundation for a variety of emergent service technology innovations such as cloud computing and Big Data, while the original building blocks of SOA and service-orientation (which include BI, BPM and MDM, among others) continue to evolve by embracing fundamental service technologies, concepts and practices.
A frequently discussed topic these days is the Micorservices architectural paradigm. Discussions on various internet blogs and forums are showing the trend that proponents of this approach are not tired of emphasizing why Microservices are different to a holistic SOA approach, when dealing with breaking up or avoiding monolithic software architectures.
For this reason it’s time for the Cattle Crew team, to take a closer look on this arising architectural style and the corresponding discussions from a different perspective.
Amongst others Martin Fowler published a blog about what is characteristic for Microservices and applications build on the foundation of this architectural style . According to this and other blog posts (see also , ), the goal of a Microservices approach is to avoid software systems to become monolithic, inflexible and hardly manageable, by splitting a system into modular, lightweight and maximum cohesive services. Applications build on this architecture should ensure the agility regarding changes caused by changed business requirements, because affected services of an application can simply be adapted and be redeployed independently from other components.
Effectively a Microservice is a in itself cohesive, atomic application, which fulfills a dedicated purpose. Therefore it encapsulates all needed elements, e.g. UIs, logic components, may also have its own separated persistent store and may run in a separate JVM, to ensure as less impairment to other services as possible. Furthermore the implementation technologies for a specific service may vary. For each service the best-fitting technology should be used; there should be no restrictions regarding the used technologies.