ºÝºÝߣshows by User: rhwinzin / http://www.slideshare.net/images/logo.gif ºÝºÝߣshows by User: rhwinzin / Sat, 16 Apr 2016 07:36:48 GMT ºÝºÝߣShare feed for ºÝºÝߣshows by User: rhwinzin Event Sourcing with Microservices /slideshow/event-sourcing-with-microservices/60983426 eventsourcingwithmicroservices-160416073648
Why do we build applications based on microservices? To gain flexibility and resilience - that’s what everybody tells us. But building and application with a lot of microservices leads to a highly distributed system - and distribution hurts! How can we keep dependencies between microservices at the lowest possible level and how can we reduce communication between them? We will have a look at „Event-Sourcing“ as a possible (and very cool) technique for asynchronous communication and data exchange/replication between microservices - in theory and also in code. ]]>
Why do we build applications based on microservices? To gain flexibility and resilience - that’s what everybody tells us. But building and application with a lot of microservices leads to a highly distributed system - and distribution hurts! How can we keep dependencies between microservices at the lowest possible level and how can we reduce communication between them? We will have a look at „Event-Sourcing“ as a possible (and very cool) technique for asynchronous communication and data exchange/replication between microservices - in theory and also in code. ]]> Sat, 16 Apr 2016 07:36:48 GMT /slideshow/event-sourcing-with-microservices/60983426 rhwinzin@slideshare.net(rhwinzin) Event Sourcing with Microservices rhwinzin Why do we build applications based on microservices? To gain flexibility and resilience - that’s what everybody tells us. But building and application with a lot of microservices leads to a highly distributed system - and distribution hurts! How can we keep dependencies between microservices at the lowest possible level and how can we reduce communication between them? We will have a look at „Event-Sourcing“ as a possible (and very cool) technique for asynchronous communication and data exchange/replication between microservices - in theory and also in code. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/eventsourcingwithmicroservices-160416073648-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Why do we build applications based on microservices? To gain flexibility and resilience - that’s what everybody tells us. But building and application with a lot of microservices leads to a highly distributed system - and distribution hurts! How can we keep dependencies between microservices at the lowest possible level and how can we reduce communication between them? We will have a look at „Event-Sourcing“ as a possible (and very cool) technique for asynchronous communication and data exchange/replication between microservices - in theory and also in code.
Event Sourcing with Microservices from Ralph Winzinger
]]> 1374 4 https://cdn.slidesharecdn.com/ss_thumbnails/eventsourcingwithmicroservices-160416073648-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Reactive Architectures /slideshow/reactive-architectures/49491361 reactivearchitecturesdwx-150617061547-lva1-app6891
We're exploring "Reactive Architectures" at Senacor Technologies. This is our view on this topic - why should we go reactive and how. It might be less than in pure theory but we need a practical approach to this topic. One that fits our company and our customers. For both worlds, we can't just throw away the existing technical steps and our skillets. Another focus of the talk is on a few topics which did hurt us in the past but usually nobody talks about them in reactive presentations.]]>
We're exploring "Reactive Architectures" at Senacor Technologies. This is our view on this topic - why should we go reactive and how. It might be less than in pure theory but we need a practical approach to this topic. One that fits our company and our customers. For both worlds, we can't just throw away the existing technical steps and our skillets. Another focus of the talk is on a few topics which did hurt us in the past but usually nobody talks about them in reactive presentations.]]> Wed, 17 Jun 2015 06:15:47 GMT /slideshow/reactive-architectures/49491361 rhwinzin@slideshare.net(rhwinzin) Reactive Architectures rhwinzin We're exploring "Reactive Architectures" at Senacor Technologies. This is our view on this topic - why should we go reactive and how. It might be less than in pure theory but we need a practical approach to this topic. One that fits our company and our customers. For both worlds, we can't just throw away the existing technical steps and our skillets. Another focus of the talk is on a few topics which did hurt us in the past but usually nobody talks about them in reactive presentations. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/reactivearchitecturesdwx-150617061547-lva1-app6891-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> We&#39;re exploring &quot;Reactive Architectures&quot; at Senacor Technologies. This is our view on this topic - why should we go reactive and how. It might be less than in pure theory but we need a practical approach to this topic. One that fits our company and our customers. For both worlds, we can&#39;t just throw away the existing technical steps and our skillets. Another focus of the talk is on a few topics which did hurt us in the past but usually nobody talks about them in reactive presentations.
Reactive Architectures from Ralph Winzinger
]]> 1364 1 https://cdn.slidesharecdn.com/ss_thumbnails/reactivearchitecturesdwx-150617061547-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Node.js - Demnächst auf einem Server in Ihrer Nähe /slideshow/nodejs-demnchst-auf-einem-server-in-ihrer-nhe/47401678 nodejshc12-150425065916-conversion-gate01
This talk is an intro to Node.js What's the history of Node.js (and JavaScript) and what can it be used for today. There's also a little bit of JavaScript basics - as much as you need to know to understand how Node.js works.]]>
This talk is an intro to Node.js What's the history of Node.js (and JavaScript) and what can it be used for today. There's also a little bit of JavaScript basics - as much as you need to know to understand how Node.js works.]]> Sat, 25 Apr 2015 06:59:15 GMT /slideshow/nodejs-demnchst-auf-einem-server-in-ihrer-nhe/47401678 rhwinzin@slideshare.net(rhwinzin) Node.js - Demnächst auf einem Server in Ihrer Nähe rhwinzin This talk is an intro to Node.js What's the history of Node.js (and JavaScript) and what can it be used for today. There's also a little bit of JavaScript basics - as much as you need to know to understand how Node.js works. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/nodejshc12-150425065916-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This talk is an intro to Node.js What&#39;s the history of Node.js (and JavaScript) and what can it be used for today. There&#39;s also a little bit of JavaScript basics - as much as you need to know to understand how Node.js works.
Node.js - Demnè¾°chst auf einem Server in Ihrer Nè¾°he from Ralph Winzinger
]]> 456 1 https://cdn.slidesharecdn.com/ss_thumbnails/nodejshc12-150425065916-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Size Does Matter - Antifragilty and Microservices /slideshow/agility-antifragility-microservices/46832970 antifragilitymicroservices-150409170157-conversion-gate01
Concepts like micro services and antifragility are currently trending in our community and this might be a hint that there are some new architecture paradigms on the horizon. Even if not, those terms describe ideas on how to not only make teams agile but also the software itself. So what are micro services and how might they help us to design and implement software systems? Well, we are using means of decomposition throughout our systems - methods, classes, packages and modules. And in the end, we put all that in a big monolith and hand it over to production … Micro services take the concept of decomposition right to our runtime environments and let us design really loose coupled systems. Those systems are built to handle the failure of single components, they are easier to test and to maintain. Last but not least, they support the idea of continuos delivery, which is also more about dealing with a lot of small changes than huge releases. The flexibility resulting here enables us to pursue one of the central paradigms of agile development not only on an organizational but also on a technical level: Embrace change!]]>
Concepts like micro services and antifragility are currently trending in our community and this might be a hint that there are some new architecture paradigms on the horizon. Even if not, those terms describe ideas on how to not only make teams agile but also the software itself. So what are micro services and how might they help us to design and implement software systems? Well, we are using means of decomposition throughout our systems - methods, classes, packages and modules. And in the end, we put all that in a big monolith and hand it over to production … Micro services take the concept of decomposition right to our runtime environments and let us design really loose coupled systems. Those systems are built to handle the failure of single components, they are easier to test and to maintain. Last but not least, they support the idea of continuos delivery, which is also more about dealing with a lot of small changes than huge releases. The flexibility resulting here enables us to pursue one of the central paradigms of agile development not only on an organizational but also on a technical level: Embrace change!]]> Thu, 09 Apr 2015 17:01:57 GMT /slideshow/agility-antifragility-microservices/46832970 rhwinzin@slideshare.net(rhwinzin) Size Does Matter - Antifragilty and Microservices rhwinzin Concepts like micro services and antifragility are currently trending in our community and this might be a hint that there are some new architecture paradigms on the horizon. Even if not, those terms describe ideas on how to not only make teams agile but also the software itself. So what are micro services and how might they help us to design and implement software systems? Well, we are using means of decomposition throughout our systems - methods, classes, packages and modules. And in the end, we put all that in a big monolith and hand it over to production … Micro services take the concept of decomposition right to our runtime environments and let us design really loose coupled systems. Those systems are built to handle the failure of single components, they are easier to test and to maintain. Last but not least, they support the idea of continuos delivery, which is also more about dealing with a lot of small changes than huge releases. The flexibility resulting here enables us to pursue one of the central paradigms of agile development not only on an organizational but also on a technical level: Embrace change! <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/antifragilitymicroservices-150409170157-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Concepts like micro services and antifragility are currently trending in our community and this might be a hint that there are some new architecture paradigms on the horizon. Even if not, those terms describe ideas on how to not only make teams agile but also the software itself. So what are micro services and how might they help us to design and implement software systems? Well, we are using means of decomposition throughout our systems - methods, classes, packages and modules. And in the end, we put all that in a big monolith and hand it over to production … Micro services take the concept of decomposition right to our runtime environments and let us design really loose coupled systems. Those systems are built to handle the failure of single components, they are easier to test and to maintain. Last but not least, they support the idea of continuos delivery, which is also more about dealing with a lot of small changes than huge releases. The flexibility resulting here enables us to pursue one of the central paradigms of agile development not only on an organizational but also on a technical level: Embrace change!
Size Does Matter - Antifragilty and Microservices from Ralph Winzinger
]]> 279 1 https://cdn.slidesharecdn.com/ss_thumbnails/antifragilitymicroservices-150409170157-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 vert.x - life beyond jetty and apache /slideshow/vertx-life-beyond-jetty-and-apache/46268647 vertx-150325083356-conversion-gate01
How to handle 10000+ parallel connections? Our digital world changes - more devices, smaller requests. Whereas multithreading was a cure some years ago, even thread context switching seems to be too much overhead now.]]>
How to handle 10000+ parallel connections? Our digital world changes - more devices, smaller requests. Whereas multithreading was a cure some years ago, even thread context switching seems to be too much overhead now.]]> Wed, 25 Mar 2015 08:33:55 GMT /slideshow/vertx-life-beyond-jetty-and-apache/46268647 rhwinzin@slideshare.net(rhwinzin) vert.x - life beyond jetty and apache rhwinzin How to handle 10000+ parallel connections? Our digital world changes - more devices, smaller requests. Whereas multithreading was a cure some years ago, even thread context switching seems to be too much overhead now. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/vertx-150325083356-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> How to handle 10000+ parallel connections? Our digital world changes - more devices, smaller requests. Whereas multithreading was a cure some years ago, even thread context switching seems to be too much overhead now.
vert.x - life beyond jetty and apache from Ralph Winzinger
]]> 2261 2 https://cdn.slidesharecdn.com/ss_thumbnails/vertx-150325083356-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation 000000 http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-rhwinzin-48x48.jpg?cb=1666169967 https://cdn.slidesharecdn.com/ss_thumbnails/eventsourcingwithmicroservices-160416073648-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/event-sourcing-with-microservices/60983426 Event Sourcing with Mi... https://cdn.slidesharecdn.com/ss_thumbnails/reactivearchitecturesdwx-150617061547-lva1-app6891-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/reactive-architectures/49491361 Reactive Architectures https://cdn.slidesharecdn.com/ss_thumbnails/nodejshc12-150425065916-conversion-gate01-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/nodejs-demnchst-auf-einem-server-in-ihrer-nhe/47401678 Node.js - Demnächst au...