Cross-platform interaction
Download as PPTX, PDF2 likes954 views
This document discusses cross-language integration and cooperation between programming languages. It begins by explaining the reasons for integration, such as lack of resources and doing things correctly. It then describes common approaches and frameworks for integration using messages, resources, and procedures. Specific integration solutions and architectures are provided as examples, like Apache Thrift. The document analyzes the different approaches and provides a sample pivot table comparing messages, resources, and procedures. Overall it provides an overview of why and how to integrate programming languages as well as examples.
Cross-platform interaction
- 1. Cross language cooperation Oleksii Dukhno @ Lohika Systems
- 2. Agenda Why? • Origin, Problems, Advantages How? • Approaches, Frameworks Samples • .NET WPF + JAVA ICP • .NET + JAVA RPC Analysis • Pivot
- 3. Why? INTEGRATION •Process of bringing together the component subsystems into one system and ensuring that the subsystems function together as a system
- 4. Why? LACK OF HUMAN RESOURCES •Customer wants to have everything and right now •Start-ups •Huge projects
- 5. Why? DO RiGHT THINGS RiGHT •Mixing programming paradigms and polyglot programming •Don’t use screwdriver for nailing •Predicting a future
- 10. How? MESSAGES – MESSAGE BUS
- 11. How? MESSAGES – MESSAGE HUB
- 12. How? MESSAGES – SOLUTIONS AMQP Exchange • receives messages from publisher applications and routes these to "message queues", based on arbitrary criteria, usually message properties or content. Message queue • stores messages until they can be safely processed by a consuming client application (or multiple applications). Binding • defines the relationship between a message queue and an exchange and provides the message routing criteria
- 13. How? MESSAGES – SOLUTIONS AMQP RabbitMQ Windows Azure Service Bus Windows Service Bus
- 17. How? RESOURCES ORIGIN REST • Fielding, Roy Thomas (2000), Architectural Styles and the Design of Network-based Software Architectures ROA and RESTfull • Richardson, Leonard; Ruby, Sam (2007). RESTful Web Services
- 18. How? RESOURCES REST constraints: Client-Server •separation of concerns Stateless •Visibility, reliability and scalability Cache •improve network efficiency, but decrease reliability Uniform Interface •simplify architecture Layered system •Flexibility but degrades latency Code on demand •Reduces number of features to be implemented
- 19. How? RESOURCES ROA concepts: Resources Resources URIs Resources Representation Links between them (hypermedia)
- 21. How? RPC SOLUTIONS XML-RPC JSON-RPC SOAP Cisco – Etch ZeroC – ICE Google - ProtoBuf Apache - Hadoop Avro Facebook - Thrift
- 22. Pivot table Messages Resources Procedures Supportability 3 3 3 Scalability 3 2 1 Performance 2 1 3 Expressiveness 1 2 3 Network Throughput 3 2 3 Total: 12 11 13
- 23. APACHE THRIFT RPC ARCHITECTURE Transport • Http • TCP Sockets • Stream • Your own Protocol packer • JSON • BSON • Your own Data generator • Generators for: As3, C Glib, C++, C#, D, Delphi, Erlang, Go, Graphviz, Haskell, Java, Java Me, Javascript, Node.js, Objective-c, OCaml, Perl, PHP, Python, Ruby, Smalltalk
- 24. Apache Thrift IDL IDLs fileJAVA branch .NET branch JAVA classes .NET classes SVN Thrift generator Thrift generator MODULE 1 MODULE 2 externals
- 25. SAMPLES
- 26. JAVA -> .NET – CALCULATOR .NET Client CLR Machine 1 JAVA server JVM Machine 2 JETTY
- 27. JAVA -> .NET – a Business App .NET Client CLR Machine JAVA server JVM WPF MS SQL 1 2 4 3
Editor's Notes
- #3: ПричиныКак достичь возможности
- #4: Integrating existing subsystemsExtending existing subsystems or applications
- #5: Finding a lot of developers using different languages and technologies is simpler then find a lot of developer using a single ones
- #6: There are three main programming paradigms:ImperativeDeclarativeFunctionalDon’t use C for programming GUIThink which subsystems will grow in future
- #7: Every language and p
- #8: PhysicalLogicalIntegration
- #9: PhysicalLogicalIntegration
- #10: Every language and p
- #11: Broadcast based message bus architecture
- #12: Content based message bus architectureDifference between that two message busses in Broker implementation
- #13: In very gross terms, an AMQP server is analogous to an email server, with each exchange acting as amessage transfer agent, and each message queue as a mailbox. The bindings define the routing tables ineach transfer agent. Publishers send messages to individual transfer agents, which then route the messagesinto mailboxes. Consumers take messages from mailboxes.
- #20: The ROA is the name we give to REST when combined with our codified version of folklore. We came up with a new term because REST isn't an architecture: it's an architectural style, a way of judging architectures. It's not even tied to HTTP. Which is fine, but it means that there's a largely undefined path from RESTful principles, to principles of HTTP-based applications, to principles of web services in particular, to the design of specific services. The ROA is a way-station along that path: an alternate starting point that gets you more quickly to the design of specific services. The ROA is a concrete architecture specifically designed for web services, with a procedure you can follow to turn requirements into resources.
- #23: Each client can call its server methods passing arguments and receiving results.For programmers it seems like creating just local application object and call methods on it.
- #25: IDL – defines protocol with services, methods and types.Thrift generates classes for both .NET and JAVA technologies.Thrift generates proxy classes to communicate with RPC (client/server).Guarantees APIs consistency and strongly typing.
- #26: Each client can call its server methods passing arguments and receiving results.For programmers it seems like creating just local application object and call methods on it.
- #27: IDL – defines protocol with services, methods and types.Thrift generates classes for both .NET and JAVA technologies.Thrift generates proxy classes to communicate with RPC (client/server).Guarantees APIs consistency and strongly typing.
- #28: IDL – defines protocol with services, methods and types.Thrift generates classes for both .NET and JAVA technologies.Thrift generates proxy classes to communicate with RPC (client/server).Guarantees APIs consistency and strongly typing.