Buffett has described car dealerships that are run well as “a very good business.” In an interview with Fortune about Berkshire Hathaway’s purchase of the Van Tuyl Group, he noted dealerships “have no receivables to speak of, you floor-plan your inventory, you can lease your real estate….So you can have very little capital actually invested in the business, and you do a large volume.”
http://www.forbes.com/sites/markewing/2014/10/20/audi-piloted-driving-success-at-hockenheimring/
Cars are getting faster, more efficient and better equipped than ever. Still, without these ten important innovations in safety, some of us wouldn’t be here today for sure.
http://jalopnik.com/the-ten-most-important-safety-advancements-in-automotiv-1462200446
Any place, any time: the old promise from the dotcom age has never been more relevant. With the release of the iPhone, Apple set off a huge amount of hype. Many people now have a laptop with broadband Internet connection and/or WLAN or UMTS Internet access. Yet these devices are still too large, too awkward, and take too long to boot up to be usable at any time. On the other hand, almost everyone has a smartphone these days, making them more mobile than ever in today’s economy. Smartphones are enormously practical and are becoming more and more powerful. They are generally very easy to operate, can be used almost anywhere, and the mobile web is becoming both faster and cheaper. App stores are shooting up everywhere and new functions can be installed with a single click. As the saying has it: “There’s an app for everything.
http://www.oracle.com/technetwork/articles/soa/ind-soa-mobile-2045748.html
Este artigo, datado de 2002, apresenta as mais diversas vantagens de utilizar uma metodologia Agile aquando da implementação de um projecto EAI. Por norma, os projectos de EAI tendem a ser bastante estritos no seu planeamento e execução. Com uma perspectiva mais ágil, alterações e imprevistos durante a sua execução são mais depressa ultrapassados, reduzindo o TTM (time-to-market) e o ROI (Return on Investment)
Este artigo explica, de forma sucinta, a diferença entre três conceitos basilares de Integração (muitas vezes confundidos): ESB, EAI e SOA. SOA é um paradigma de integração – visa a atomização de serviços. EAI (Enterprise Application Integration) é uma framework que visa a integração de dados entre várias aplicações na numa organização. ESB (Enterprise Service Bus) é uma arquitectura que possibilita a comunicação entre aplicações.
Some of the most important SOA design patterns that we have successfully applied in projects will be described in this article. These include the Compensation pattern and the UI mediator pattern, the Common Data Format pattern and the Data Access pattern. All of these patterns are included in Thomas Erl’s book, “SOA Design Patterns”, and are presented here in detail, together with our practical experiences. We begin our “best of” SOA pattern collection with the Compensation pattern.
http://www.oracle.com/technetwork/articles/soa/ind-soa-7-service-comp-2005463.html
Este artigo apesar de ser escrito para Cloud Providers, é também muito interessante para outras pessoas que se interessem pela área, visto que, desmistifica alguns aspectos sobre SOA.
Security requirements are usually relatively easy to manage when using local restrictions in conventional closed systems. They become more complex in the distributed system landscape of an SOA. Not limited to only an application or an application domain anymore, security must work across a range of applications and business processes. Numerous security standards have been created in order to realize these comprehensive security requirements. These include WS-SecurityPolicy, WS-Trust, XML Encryption, XKMS, XML Signature, WS-Federation, WS-SecureConversation, SAML1, SAML2, and many more. Currently, no product or open source framework can fully support all of these standards. In our experience, incompatibilities arise whenever an SOA product or deployed Web service framework needs to communicate outside of its small ecosystem.
http://www.oracle.com/technetwork/articles/soa/ind-soa-6-security-1980268.html
Services have to meet different architecture and governance requirements whose relevance is determined by how the services are reused. The arrangement and structure significantly affect the analysis and design of the services, which in turn determine the level of granularity. Categorizing services makes it easier to arrange them according to service usage in the procedural landscape, which helps prevent unwanted entanglements. SOA architectures that have not undergone categorization quickly become “adapter” SOAs that lack a clear division of responsibilities. The orchestration of business processes in these architectures is interspersed with technical service calls that can lead to unaccountable call sequences.
http://www.oracle.com/technetwork/articles/soa/ind-soa-canonizing-language-1957510.html
