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
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
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
27. JAVA -> .NET – a Business App
.NET
Client
CLR
Machine
JAVA
server
JVM
WPF
MS SQL
1 2
4 3
Hinweis der Redaktion
ПричиныКак достичь возможности
Integrating existing subsystemsExtending existing subsystems or applications
Finding a lot of developers using different languages and technologies is simpler then find a lot of developer using a single ones
There are three main programming paradigms:ImperativeDeclarativeFunctionalDon’t use C for programming GUIThink which subsystems will grow in future
Every language and p
PhysicalLogicalIntegration
PhysicalLogicalIntegration
Every language and p
Broadcast based message bus architecture
Content based message bus architectureDifference between that two message busses in Broker implementation
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.
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.
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.
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.
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.
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.
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.