�ݺ�ߣshows by User: pgte

�ݺ�ߣshows by User: pgte / http://www.slideshare.net/images/logo.gif �ݺ�ߣshows by User: pgte / Sat, 28 Oct 2017 11:00:10 GMT �ݺ�ߣShare feed for �ݺ�ߣshows by User: pgte Building Decentralised Realtime Collaborative Applications - Building Google Docs without Google /slideshow/building-decentralised-realtime-collaborative-applications-building-google-docs-without-google/81314548 p2p-flipchart-171028110010
Using IPFS, Y.js and CRDT.]]>
Using IPFS, Y.js and CRDT.]]> Sat, 28 Oct 2017 11:00:10 GMT /slideshow/building-decentralised-realtime-collaborative-applications-building-google-docs-without-google/81314548 pgte@slideshare.net(pgte) Building Decentralised Realtime Collaborative Applications - Building Google Docs without Google pgte Using IPFS, Y.js and CRDT. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/p2p-flipchart-171028110010-thumbnail.jpg?width=120&height=120&fit=bounds" /> Using IPFS, Y.js and CRDT.

Building Decentralised Realtime Collaborative Applications - Building Google Docs without Google from Pedro Teixeira

]]> 2697 4 https://cdn.slidesharecdn.com/ss_thumbnails/p2p-flipchart-171028110010-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 Offline-first: Making your app resilient to network failures /slideshow/offlinefirst-making-your-app-resilient-to-network-failures/75426963 presentation-170426120929
Mobile networks are unreliable, and the user experience is often hurt. "Works on my computer" is no longer an acceptable excuse. I'll show the audience some techniques to improve your users' experience.]]>
Mobile networks are unreliable, and the user experience is often hurt. "Works on my computer" is no longer an acceptable excuse. I'll show the audience some techniques to improve your users' experience.]]> Wed, 26 Apr 2017 12:09:28 GMT /slideshow/offlinefirst-making-your-app-resilient-to-network-failures/75426963 pgte@slideshare.net(pgte) Offline-first: Making your app resilient to network failures pgte Mobile networks are unreliable, and the user experience is often hurt. "Works on my computer" is no longer an acceptable excuse. I'll show the audience some techniques to improve your users' experience. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/presentation-170426120929-thumbnail.jpg?width=120&height=120&fit=bounds" /> Mobile networks are unreliable, and the user experience is often hurt. "Works on my computer" is no longer an acceptable excuse. I'll show the audience some techniques to improve your users' experience.

Offline-first: Making your app resilient to network failures from Pedro Teixeira

]]> 235 3 https://cdn.slidesharecdn.com/ss_thumbnails/presentation-170426120929-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 How to build a reliable checkout experience /pgte/how-to-build-a-reliable-checkout-experience-66857209 presentation-161007130236
The checkout experience is usually the one part of the application that delivers the most value, but unfortunately, it's the one that usually contains the most friction. We've all been victims of this: a checkout experience that has spinner that spins indefinitely, or one that warns you to not move a muscle while the next page is loading, or even one that makes a double reservation. Now that you have your shiny new micro-services architecture running and you're able to deploy new features and fixes several times a day, how do you deliver complex transactions to your customers? How do you deliver payments, trip reservations or purchasing an entire shopping cart with a good user experience? HTTP has taken us far, but it's probably not the best transport to deliver complex transactions like these, specially when these transactions are performed over flaky mobile networks. A lot of error-handling logic must fall on the client: How does the client react to timeouts? Or gateway problems? Can it assume the transaction failed with no fear of duplication? Can the transaction survive client crashes? Can the client solve all these existing edge cases without making it overly complex and bug-prone? This talk proposes an original architecture style that will sit in front of your micro-service stack and that you can attach to any existing service back-end. The author will show an implementation of this architecture pattern: a proof-of-concept application and a set of client and server open-source libraries built on top of PouchDB, and Node.js.]]>
The checkout experience is usually the one part of the application that delivers the most value, but unfortunately, it's the one that usually contains the most friction. We've all been victims of this: a checkout experience that has spinner that spins indefinitely, or one that warns you to not move a muscle while the next page is loading, or even one that makes a double reservation. Now that you have your shiny new micro-services architecture running and you're able to deploy new features and fixes several times a day, how do you deliver complex transactions to your customers? How do you deliver payments, trip reservations or purchasing an entire shopping cart with a good user experience? HTTP has taken us far, but it's probably not the best transport to deliver complex transactions like these, specially when these transactions are performed over flaky mobile networks. A lot of error-handling logic must fall on the client: How does the client react to timeouts? Or gateway problems? Can it assume the transaction failed with no fear of duplication? Can the transaction survive client crashes? Can the client solve all these existing edge cases without making it overly complex and bug-prone? This talk proposes an original architecture style that will sit in front of your micro-service stack and that you can attach to any existing service back-end. The author will show an implementation of this architecture pattern: a proof-of-concept application and a set of client and server open-source libraries built on top of PouchDB, and Node.js.]]> Fri, 07 Oct 2016 13:02:36 GMT /pgte/how-to-build-a-reliable-checkout-experience-66857209 pgte@slideshare.net(pgte) How to build a reliable checkout experience pgte The checkout experience is usually the one part of the application that delivers the most value, but unfortunately, it's the one that usually contains the most friction. We've all been victims of this: a checkout experience that has spinner that spins indefinitely, or one that warns you to not move a muscle while the next page is loading, or even one that makes a double reservation. Now that you have your shiny new micro-services architecture running and you're able to deploy new features and fixes several times a day, how do you deliver complex transactions to your customers? How do you deliver payments, trip reservations or purchasing an entire shopping cart with a good user experience? HTTP has taken us far, but it's probably not the best transport to deliver complex transactions like these, specially when these transactions are performed over flaky mobile networks. A lot of error-handling logic must fall on the client: How does the client react to timeouts? Or gateway problems? Can it assume the transaction failed with no fear of duplication? Can the transaction survive client crashes? Can the client solve all these existing edge cases without making it overly complex and bug-prone? This talk proposes an original architecture style that will sit in front of your micro-service stack and that you can attach to any existing service back-end. The author will show an implementation of this architecture pattern: a proof-of-concept application and a set of client and server open-source libraries built on top of PouchDB, and Node.js. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/presentation-161007130236-thumbnail.jpg?width=120&height=120&fit=bounds" /> The checkout experience is usually the one part of the application that delivers the most value, but unfortunately, it's the one that usually contains the most friction. We've all been victims of this: a checkout experience that has spinner that spins indefinitely, or one that warns you to not move a muscle while the next page is loading, or even one that makes a double reservation. Now that you have your shiny new micro-services architecture running and you're able to deploy new features and fixes several times a day, how do you deliver complex transactions to your customers? How do you deliver payments, trip reservations or purchasing an entire shopping cart with a good user experience? HTTP has taken us far, but it's probably not the best transport to deliver complex transactions like these, specially when these transactions are performed over flaky mobile networks. A lot of error-handling logic must fall on the client: How does the client react to timeouts? Or gateway problems? Can it assume the transaction failed with no fear of duplication? Can the transaction survive client crashes? Can the client solve all these existing edge cases without making it overly complex and bug-prone? This talk proposes an original architecture style that will sit in front of your micro-service stack and that you can attach to any existing service back-end. The author will show an implementation of this architecture pattern: a proof-of-concept application and a set of client and server open-source libraries built on top of PouchDB, and Node.js.

How to build a reliable checkout experience from Pedro Teixeira

]]> 436 2 https://cdn.slidesharecdn.com/ss_thumbnails/presentation-161007130236-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 How to build a reliable checkout experience /slideshow/how-to-build-a-reliable-checkout-experience/66086604 buildingareliablecheckoutexperience-160916081657
uUsing Node.js, PouchDB and Replicated Transaction Documents]]>
uUsing Node.js, PouchDB and Replicated Transaction Documents]]> Fri, 16 Sep 2016 08:16:57 GMT /slideshow/how-to-build-a-reliable-checkout-experience/66086604 pgte@slideshare.net(pgte) How to build a reliable checkout experience pgte uUsing Node.js, PouchDB and Replicated Transaction Documents <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/buildingareliablecheckoutexperience-160916081657-thumbnail.jpg?width=120&height=120&fit=bounds" /> uUsing Node.js, PouchDB and Replicated Transaction Documents

How to build a reliable checkout experience from Pedro Teixeira

]]> 1070 4 https://cdn.slidesharecdn.com/ss_thumbnails/buildingareliablecheckoutexperience-160916081657-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 Document-Driven transactions /pgte/documentdriven-transactions document-driven-transactions-160714122839
Presentation: https://www.youtube.com/watch?v=2yb0tn3Q3Mg]]>
Presentation: https://www.youtube.com/watch?v=2yb0tn3Q3Mg]]> Thu, 14 Jul 2016 12:28:38 GMT /pgte/documentdriven-transactions pgte@slideshare.net(pgte) Document-Driven transactions pgte Presentation: https://www.youtube.com/watch?v=2yb0tn3Q3Mg <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/document-driven-transactions-160714122839-thumbnail.jpg?width=120&height=120&fit=bounds" /> Presentation: https://www.youtube.com/watch?v=2yb0tn3Q3Mg

Document-Driven transactions from Pedro Teixeira

]]> 222 4 https://cdn.slidesharecdn.com/ss_thumbnails/document-driven-transactions-160714122839-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 Anti-Patterns and Bad Practices /slideshow/node-antipatterns-and-bad-practices/59270915 node-antipatterns-qcon-160308174720
Node is fundamentally different from the other technologies frequently used in big teams. Adopting Node also means adopting its newer practices.]]>
Node is fundamentally different from the other technologies frequently used in big teams. Adopting Node also means adopting its newer practices.]]> Tue, 08 Mar 2016 17:47:19 GMT /slideshow/node-antipatterns-and-bad-practices/59270915 pgte@slideshare.net(pgte) Node Anti-Patterns and Bad Practices pgte Node is fundamentally different from the other technologies frequently used in big teams. Adopting Node also means adopting its newer practices. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/node-antipatterns-qcon-160308174720-thumbnail.jpg?width=120&height=120&fit=bounds" /> Node is fundamentally different from the other technologies frequently used in big teams. Adopting Node also means adopting its newer practices.

Node Anti-Patterns and Bad Practices from Pedro Teixeira

]]> 1909 6 https://cdn.slidesharecdn.com/ss_thumbnails/node-antipatterns-qcon-160308174720-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 a-deep-dive 2-final /slideshow/nodejs-adeepdive-2final/5783332 node-js-a-deep-dive2final-101115052041-phpapp01
]]>
]]> Mon, 15 Nov 2010 05:20:28 GMT /slideshow/nodejs-adeepdive-2final/5783332 pgte@slideshare.net(pgte) Node.js a-deep-dive 2-final pgte <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/node-js-a-deep-dive2final-101115052041-phpapp01-thumbnail.jpg?width=120&height=120&fit=bounds" />

Node.js a-deep-dive 2-final from Pedro Teixeira

]]> 1444 2 https://cdn.slidesharecdn.com/ss_thumbnails/node-js-a-deep-dive2final-101115052041-phpapp01-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 https://cdn.slidesharecdn.com/profile-photo-pgte-48x48.jpg?cb=1587804850 Software Engineer. Writer. Conference Organizer. Entrepreneur. http://metaduck.com https://cdn.slidesharecdn.com/ss_thumbnails/p2p-flipchart-171028110010-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/building-decentralised-realtime-collaborative-applications-building-google-docs-without-google/81314548 Building Decentralised... https://cdn.slidesharecdn.com/ss_thumbnails/presentation-170426120929-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/offlinefirst-making-your-app-resilient-to-network-failures/75426963 Offline-first: Making ... https://cdn.slidesharecdn.com/ss_thumbnails/presentation-161007130236-thumbnail.jpg?width=320&height=320&fit=bounds pgte/how-to-build-a-reliable-checkout-experience-66857209 How to build a reliabl...