Dlsecyx pgroammr (Dyslexic Programmer - cool stuff for scaling)
•
3 likes•5,358 views
This document discusses asynchronous and non-blocking I/O models in various programming languages like Ruby, Python, Node.js, and Erlang. It provides code examples for implementing URL fetching using blocking vs non-blocking I/O in Ruby and Python. It also summarizes concepts like generators, deferreds, callbacks and event loops in different asynchronous programming models.
Report
Share
Report
Share
Download to read offline
Recommended
Architecture by Accident
This document discusses how architecture emerges even when not initially planned. It begins with an overview of databases, message queues, and caching as common architectural elements that emerge over time. The document then provides examples of how simple applications and data needs can evolve into more complex architectures with multiple servers, databases, caching, and services. It emphasizes that architectures tend to grow more elaborate with each new system as ideas are carried over from previous projects.
Testing Storm components with Groovy and Spock
Ho to use Groovy and Spock framework for testing Java projects. Examples of using Storm testing facility.
Multithreading in C# - pitfalls, mistakes and solutions.
The document discusses common mistakes developers make with multithreading in C# applications. It includes an agenda that covers a brief overview of threads, thread overuse, and a thread overview. The presentation provides examples from a GitHub repository and discusses questions and additional learning materials on the topic of multithreading.
C++ 11 Style : A Touch of Class
The document discusses principles of writing good C++ code. It begins by criticizing existing code examples as "ghastly style" that are difficult to understand and maintain. It advocates for a type-rich interface style with compact data structures and well-structured algorithms. The document also emphasizes writing code with modularity, effective resource management, and thread safety by default. The presentation provides examples demonstrating these principles using C++11 features like auto, type aliases, and literals.
Message Queues & Offline Processing with PHP
This document discusses offline processing and message queues. It explains that offline processing involves queuing, prioritizing, dispatching, and executing background jobs from initiating processes. It then evaluates several popular message queue solutions, including Amazon SQS, Gearman, Dropr, Apache ActiveMQ, Beanstalkd, and custom solutions. It notes the pros and cons of each system in terms of features, performance, ease of use, programming language support, and other factors. The document concludes with a brief plug for the author's company CROSCON and contact information.
NDC London 2014: Erlang Patterns Matching Business Needs
Covers what makes Erlang unique.
The Golden Trinity of Erlang.
Deliver business value using the supervisor patterns.
Coldfusion
Cold Fusion is a server-side scripting language ideal for rapidly building and deploying scalable web applications without needing browser plugins. It uses tag-based syntax similar to HTML and integrates easily with all major databases. While more expensive initially than PHP, Cold Fusion provides robust debugging tools and state management. For developing basic to advanced database-driven websites, Cold Fusion offers a relatively short learning curve and strong support community.
Dark side of JS development framework
UI is the first thing which sells your application and it has been a while since we have thought to look for an alternative framework for developing UI other than Javascript. Suddenly the adoption of JS based framework like AngularJS, ReactJS, UI5 and D3JS have made Javascript the de-facto standard to create and build your UI. But is it the only option we have and the bigger question is why or why not some other tech stack replaces Javascript on UI.
Know the dark side of the Javascript frameworks for building UI, its limitation, its bad parts and learn to which extent you can push Javascript while developing UI.
Stay Connected with us!
Mail us: admin@ui5cn.com connect@ui5cn.com
Youtube: https://www.youtube.com/c/UI5CommunityNetwork?sub_confirmation=1
Facebook: https://www.facebook.com/goui5cn
Twitter: https://twitter.com/ui5cn
Google+ : https://plus.google.com/+UI5CommunityNetwork
Recommended
Architecture by Accident
This document discusses how architecture emerges even when not initially planned. It begins with an overview of databases, message queues, and caching as common architectural elements that emerge over time. The document then provides examples of how simple applications and data needs can evolve into more complex architectures with multiple servers, databases, caching, and services. It emphasizes that architectures tend to grow more elaborate with each new system as ideas are carried over from previous projects.
Testing Storm components with Groovy and Spock
Ho to use Groovy and Spock framework for testing Java projects. Examples of using Storm testing facility.
Multithreading in C# - pitfalls, mistakes and solutions.
The document discusses common mistakes developers make with multithreading in C# applications. It includes an agenda that covers a brief overview of threads, thread overuse, and a thread overview. The presentation provides examples from a GitHub repository and discusses questions and additional learning materials on the topic of multithreading.
C++ 11 Style : A Touch of Class
The document discusses principles of writing good C++ code. It begins by criticizing existing code examples as "ghastly style" that are difficult to understand and maintain. It advocates for a type-rich interface style with compact data structures and well-structured algorithms. The document also emphasizes writing code with modularity, effective resource management, and thread safety by default. The presentation provides examples demonstrating these principles using C++11 features like auto, type aliases, and literals.
Message Queues & Offline Processing with PHP
This document discusses offline processing and message queues. It explains that offline processing involves queuing, prioritizing, dispatching, and executing background jobs from initiating processes. It then evaluates several popular message queue solutions, including Amazon SQS, Gearman, Dropr, Apache ActiveMQ, Beanstalkd, and custom solutions. It notes the pros and cons of each system in terms of features, performance, ease of use, programming language support, and other factors. The document concludes with a brief plug for the author's company CROSCON and contact information.
NDC London 2014: Erlang Patterns Matching Business Needs
Covers what makes Erlang unique.
The Golden Trinity of Erlang.
Deliver business value using the supervisor patterns.
Coldfusion
Cold Fusion is a server-side scripting language ideal for rapidly building and deploying scalable web applications without needing browser plugins. It uses tag-based syntax similar to HTML and integrates easily with all major databases. While more expensive initially than PHP, Cold Fusion provides robust debugging tools and state management. For developing basic to advanced database-driven websites, Cold Fusion offers a relatively short learning curve and strong support community.
Dark side of JS development framework
UI is the first thing which sells your application and it has been a while since we have thought to look for an alternative framework for developing UI other than Javascript. Suddenly the adoption of JS based framework like AngularJS, ReactJS, UI5 and D3JS have made Javascript the de-facto standard to create and build your UI. But is it the only option we have and the bigger question is why or why not some other tech stack replaces Javascript on UI.
Know the dark side of the Javascript frameworks for building UI, its limitation, its bad parts and learn to which extent you can push Javascript while developing UI.
Stay Connected with us!
Mail us: admin@ui5cn.com connect@ui5cn.com
Youtube: https://www.youtube.com/c/UI5CommunityNetwork?sub_confirmation=1
Facebook: https://www.facebook.com/goui5cn
Twitter: https://twitter.com/ui5cn
Google+ : https://plus.google.com/+UI5CommunityNetwork
2009 Eclipse Con
The document discusses performance testing of various programming languages running on the Java Virtual Machine (JVM). It describes running a simple looping benchmark in Java, Scala, Clojure, JRuby, JPC and JavaScript to see how well each language's bytecodes can be optimized by the JIT compiler. The results show that Java and Scala perform similarly due to similar semantics, while other languages encounter issues like object allocation, lack of inlining, or data type mismatches. The author advocates for tools to help language implementers understand JVM optimization barriers and ensure their languages can achieve high performance.
Erlang White Label
Geoff Cant Whitelabel Erlang covers the trials, tribulations and technologies used in building a whitelabel ejabberd hosting service.
The talk explains the rationale behind the choices of web server, templating system, email module, page optimizers and other web framework components. The talk also covers the documented and undocumented DNS query and caching modules in OTP and introduces 'dns' - a convenient new API for using them. Finally, the talk describes some tips and tricks useful for whitelabel hosting solutions that require customer DNS updates.
Why you should use a web framework, eventually
The document discusses the author's journey developing a student application from scratch without a framework. It describes the challenges faced with a complex and rushed project. This led to issues with code quality, efficiency, and maintainability. The author then introduces Laravel, noting how it addressed these problems through features like database abstraction, routing, and API support. It allowed the project to be rebuilt faster and at a higher quality level. The conclusion emphasizes how frameworks save development time but starting without one provides important learning experiences.
Thinking Functionally
This document provides an opinionated guide to thinking functionally as a software architect. It recommends starting with Racket to learn functional programming concepts like recursion, higher order functions, and avoiding mutations. Some key aspects of functional programming discussed are using functions as first-class citizens, favoring recursion over iteration, laziness with streams, expressions over statements, and composition over inheritance. The document also mentions concepts like closures, pattern matching, currying, and persistent data structures. It recommends resources for learning more about functional programming in Racket, Lisp, Haskell, F#, OCaml, and Idris.
Web performance
what's thing we should think about during the performance journey . Major help you to solve these problem .
Illustrated Code (ASE 2021)
Illustrated Code: Building Software in a Literate Way
Andreas Zeller, CISPA Helmholtz Center for Information Security
Notebooks – rich, interactive documents that join together code, documentation, and outputs – are all the rage with data scientists. But can they be used for actual software development? In this talk, I share experiences from authoring two interactive textbooks – fuzzingbook.org and debuggingbook.org – and show how notebooks not only serve for exploring and explaining code and data, but also how they can be used as software modules, integrating self-checking documentation, tests, and tutorials all in one place. The resulting software focuses on the essential, is well-documented, highly maintainable, easily extensible, and has a much higher shelf life than the "duct tape and wire” prototypes frequently found in research and beyond.
Web Development with Smalltalk
"Web Development with Smalltalk" presentation at "Summer School on Languages and Applications" 2014 in Cochabamba, Bolivia.
Salesforce Apex Ten Commandments
This document outlines 10 commandments for writing efficient and well-structured Apex code in Salesforce. The commandments advise practices like limiting queries and DML operations in loops, having a single trigger per object, utilizing relationships and maps to reduce queries, writing unit tests with 100% code coverage that test all logic branches, limiting future calls and using asynchronous code where possible, and writing batch Apex that is efficiently optimized. The document provides examples and explanations for each commandment and invites questions from the reader.
A first look into the Project Loom in Java
Project Loom aims to bring asynchronous programming to Java with virtual threads. Virtual threads allow blocking code to run asynchronously by scheduling continuations across lightweight threads. This avoids the "blue world" problem of rewriting synchronous code for asynchronous systems. It also enables scaling applications by utilizing non-blocking I/O without changing existing code or libraries. While virtual threads are not yet production-ready, Project Loom has the potential to improve scalability for Java applications without a major paradigm shift.
Reactive programming
The document discusses reactive programming and provides examples using RxJS. It defines reactive programming as working with asynchronous data streams. Streams can represent events like user inputs or API responses. Key concepts discussed include:
- Observables represent streams of data that can be subscribed to. Common stream operations like map, filter, and scan can transform streams.
- An example demonstrates creating a stream for a "Who to follow" API, making a request on startup and refresh, and rendering responses.
- Other operators like merge, startWith, and combineLatest are used to combine multiple streams of events and responses.
Reactive programming intro
An introduction to reactive programming concepts and basics. I aim here to show what's reactive programming, why it's used and show some frameworks and benchmarks that support it.
Art of Disorderly Programming
This talk will cover effects of enforcing time order on performance. The logic which is time order dependent will need some sort of locking to enforce time order. In case of in-memory computing and that too distributed in nature, it becomes a problem. The ratio of "cost of an operation on a single node/single shard" to "cost of locking and coherency" is going to be high as compared to traditional disk-based systems. This can be analyzed using Little's law and Amdahl's law. Further, I would cover techniques to structure program logic to get around ordering and associated cost.
TBP程式新手懶人包
This document provides an overview of resources for learning to code including programming languages, frameworks, and tools. It discusses the evolution of front-end technologies from LAMP stacks and Ruby on Rails to modern JavaScript frameworks. Codecademy, Udacity, Udemy, edX, and textbooks are recommended for learning. Tools mentioned include Codewars, Project Euler, and Codepen for practicing, text editors, GitHub, terminals, and PaaS for building projects, and Stack Overflow and meetups for problem solving. The 12 in 12 challenge encourages learning a new technology each month and sharing projects.
ScalaItaly 2015 - Your Microservice as a Function
SoundCloud's microservice architecture is built mostly in Scala, using Finagle as its distributed systems workhorse. Finagle is an RPC system for the JVM, and it is based on a pipes-and-filters architecture that maps very nicely to functional programming concepts of higher-order functions and combinators. Over the past few years we have found that it is extremely useful to go even a step further and think of microservices as functions themselves. In this talk let's explore how SoundCloud uses Scala and Finagle, and how we started thinking of a microservices architecture as a special case of a functional system.
Writing code for people
Writing code that works and writing code that other people can read and understand are two different skills. And writing code that other people can read and understand became more and more essential skills as the project grows larger, and more people start working on it.
But because it is a skill, you need to train it consciously. It's a lot like writing essays and books. Everybody can write letters and words; many can also connect them in grammatically correct sentences. But not everybody is a J. R. R. R. Tolkien and have their books read by everyone.
An essential part of learning this skill is reading and analyzing other people's code on the one hand. And making other people read your code and give you feedback about it.
The speaker will talk about different methods of how to make programmers better writers and how to work out the skill of writing code that other people will want to read.
scaling compiled applications - highload 2013
my talk from highload++ 2013 -- talking about scaling compiled applications but from the point of view of scaling up from supporting 1 platform to supporting MANY platforms.
in other words: given an application that supports ubuntu 10.04, what sort of systems, tips, and tricks are needed to help scale support to other ubuntus, redhats, centos, windows, etc.
Functional reactive programming
This document provides an overview of functional reactive programming (FRP). It begins by discussing programming paradigms like imperative and declarative programming. FRP is then introduced as a programming paradigm that combines functional programming and reactive programming. Functional programming treats computation as mathematical functions while reactive programming involves asynchronous data streams. The document explains core FRP concepts like streams and signals. It also introduces RxSwift, a library that brings FRP to iOS. Finally, examples are provided to demonstrate the advantages of using an FRP approach.
Metaprogramming JavaScript
JavaScript allows for metaprogramming through manipulating programs as data. It relies on few but powerful constructs including working with functions, arguments, built-in types, and mechanisms like inheritance at runtime. The key building blocks are objects, numbers, strings, booleans, and undefined, with everything else being objects. Functions are objects that can return other functions, taking advantage of closures to refer to outer variables from inner functions. This flexibility allows for patching implementations, self-optimizing code, custom APIs, and domain-specific languages.
Varnish to the rescue
What is Varnish reverse proxy server, how to configure it, how can it help with day to day problems of a web application.
RestMQ - HTTP/Redis based Message Queue
RestMQ is a message queue system based on Redis that allows storing and retrieving messages through HTTP requests. It uses Redis' data structures like lists, sets, and hashes to maintain queues and messages. Messages can be added to and received from queues using RESTful endpoints. Additional features include status monitoring, queue control, and support for protocols like JSON, Comet, and WebSockets. The core functionality is language-agnostic but implementations exist in Python and Ruby.
Redis
Redis is a key-value store that provides common data structures like lists, sets, and ordered sets as building blocks. It offers features like asynchronous I/O, fast operations, active development, and different persistence strategies. RestMQ is a message queue built on Redis that uses HTTP, REST, and JSON. It provides COMET consumer functionality and integrates with an asynchronous Redis client and Twisted-based web framework called Cyclone. DOCDB is a prototype document database that indexes documents by tokenizing, removing stop words, stemming words, and grouping them into Redis sets to allow searching by keywords.
NoSQL and SQL Anti Patterns
This document provides examples of common SQL anti-patterns and related NoSQL alternatives. It discusses issues like using tables as trees, caches, queues, or logs. It also addresses dynamic schema/table creation, stored procedures, row padding, complex joins, and object-relational mismatches. The document recommends alternatives like document databases, key-value stores, message brokers, and denormalization. It includes examples of modeling book data in MongoDB and Redis.
More Related Content
What's hot
2009 Eclipse Con
The document discusses performance testing of various programming languages running on the Java Virtual Machine (JVM). It describes running a simple looping benchmark in Java, Scala, Clojure, JRuby, JPC and JavaScript to see how well each language's bytecodes can be optimized by the JIT compiler. The results show that Java and Scala perform similarly due to similar semantics, while other languages encounter issues like object allocation, lack of inlining, or data type mismatches. The author advocates for tools to help language implementers understand JVM optimization barriers and ensure their languages can achieve high performance.
Erlang White Label
Geoff Cant Whitelabel Erlang covers the trials, tribulations and technologies used in building a whitelabel ejabberd hosting service.
The talk explains the rationale behind the choices of web server, templating system, email module, page optimizers and other web framework components. The talk also covers the documented and undocumented DNS query and caching modules in OTP and introduces 'dns' - a convenient new API for using them. Finally, the talk describes some tips and tricks useful for whitelabel hosting solutions that require customer DNS updates.
Why you should use a web framework, eventually
The document discusses the author's journey developing a student application from scratch without a framework. It describes the challenges faced with a complex and rushed project. This led to issues with code quality, efficiency, and maintainability. The author then introduces Laravel, noting how it addressed these problems through features like database abstraction, routing, and API support. It allowed the project to be rebuilt faster and at a higher quality level. The conclusion emphasizes how frameworks save development time but starting without one provides important learning experiences.
Thinking Functionally
This document provides an opinionated guide to thinking functionally as a software architect. It recommends starting with Racket to learn functional programming concepts like recursion, higher order functions, and avoiding mutations. Some key aspects of functional programming discussed are using functions as first-class citizens, favoring recursion over iteration, laziness with streams, expressions over statements, and composition over inheritance. The document also mentions concepts like closures, pattern matching, currying, and persistent data structures. It recommends resources for learning more about functional programming in Racket, Lisp, Haskell, F#, OCaml, and Idris.
Web performance
what's thing we should think about during the performance journey . Major help you to solve these problem .
Illustrated Code (ASE 2021)
Illustrated Code: Building Software in a Literate Way
Andreas Zeller, CISPA Helmholtz Center for Information Security
Notebooks – rich, interactive documents that join together code, documentation, and outputs – are all the rage with data scientists. But can they be used for actual software development? In this talk, I share experiences from authoring two interactive textbooks – fuzzingbook.org and debuggingbook.org – and show how notebooks not only serve for exploring and explaining code and data, but also how they can be used as software modules, integrating self-checking documentation, tests, and tutorials all in one place. The resulting software focuses on the essential, is well-documented, highly maintainable, easily extensible, and has a much higher shelf life than the "duct tape and wire” prototypes frequently found in research and beyond.
Web Development with Smalltalk
"Web Development with Smalltalk" presentation at "Summer School on Languages and Applications" 2014 in Cochabamba, Bolivia.
Salesforce Apex Ten Commandments
This document outlines 10 commandments for writing efficient and well-structured Apex code in Salesforce. The commandments advise practices like limiting queries and DML operations in loops, having a single trigger per object, utilizing relationships and maps to reduce queries, writing unit tests with 100% code coverage that test all logic branches, limiting future calls and using asynchronous code where possible, and writing batch Apex that is efficiently optimized. The document provides examples and explanations for each commandment and invites questions from the reader.
A first look into the Project Loom in Java
Project Loom aims to bring asynchronous programming to Java with virtual threads. Virtual threads allow blocking code to run asynchronously by scheduling continuations across lightweight threads. This avoids the "blue world" problem of rewriting synchronous code for asynchronous systems. It also enables scaling applications by utilizing non-blocking I/O without changing existing code or libraries. While virtual threads are not yet production-ready, Project Loom has the potential to improve scalability for Java applications without a major paradigm shift.
Reactive programming
The document discusses reactive programming and provides examples using RxJS. It defines reactive programming as working with asynchronous data streams. Streams can represent events like user inputs or API responses. Key concepts discussed include:
- Observables represent streams of data that can be subscribed to. Common stream operations like map, filter, and scan can transform streams.
- An example demonstrates creating a stream for a "Who to follow" API, making a request on startup and refresh, and rendering responses.
- Other operators like merge, startWith, and combineLatest are used to combine multiple streams of events and responses.
Reactive programming intro
An introduction to reactive programming concepts and basics. I aim here to show what's reactive programming, why it's used and show some frameworks and benchmarks that support it.
Art of Disorderly Programming
This talk will cover effects of enforcing time order on performance. The logic which is time order dependent will need some sort of locking to enforce time order. In case of in-memory computing and that too distributed in nature, it becomes a problem. The ratio of "cost of an operation on a single node/single shard" to "cost of locking and coherency" is going to be high as compared to traditional disk-based systems. This can be analyzed using Little's law and Amdahl's law. Further, I would cover techniques to structure program logic to get around ordering and associated cost.
TBP程式新手懶人包
This document provides an overview of resources for learning to code including programming languages, frameworks, and tools. It discusses the evolution of front-end technologies from LAMP stacks and Ruby on Rails to modern JavaScript frameworks. Codecademy, Udacity, Udemy, edX, and textbooks are recommended for learning. Tools mentioned include Codewars, Project Euler, and Codepen for practicing, text editors, GitHub, terminals, and PaaS for building projects, and Stack Overflow and meetups for problem solving. The 12 in 12 challenge encourages learning a new technology each month and sharing projects.
ScalaItaly 2015 - Your Microservice as a Function
SoundCloud's microservice architecture is built mostly in Scala, using Finagle as its distributed systems workhorse. Finagle is an RPC system for the JVM, and it is based on a pipes-and-filters architecture that maps very nicely to functional programming concepts of higher-order functions and combinators. Over the past few years we have found that it is extremely useful to go even a step further and think of microservices as functions themselves. In this talk let's explore how SoundCloud uses Scala and Finagle, and how we started thinking of a microservices architecture as a special case of a functional system.
Writing code for people
Writing code that works and writing code that other people can read and understand are two different skills. And writing code that other people can read and understand became more and more essential skills as the project grows larger, and more people start working on it.
But because it is a skill, you need to train it consciously. It's a lot like writing essays and books. Everybody can write letters and words; many can also connect them in grammatically correct sentences. But not everybody is a J. R. R. R. Tolkien and have their books read by everyone.
An essential part of learning this skill is reading and analyzing other people's code on the one hand. And making other people read your code and give you feedback about it.
The speaker will talk about different methods of how to make programmers better writers and how to work out the skill of writing code that other people will want to read.
scaling compiled applications - highload 2013
my talk from highload++ 2013 -- talking about scaling compiled applications but from the point of view of scaling up from supporting 1 platform to supporting MANY platforms.
in other words: given an application that supports ubuntu 10.04, what sort of systems, tips, and tricks are needed to help scale support to other ubuntus, redhats, centos, windows, etc.
Functional reactive programming
This document provides an overview of functional reactive programming (FRP). It begins by discussing programming paradigms like imperative and declarative programming. FRP is then introduced as a programming paradigm that combines functional programming and reactive programming. Functional programming treats computation as mathematical functions while reactive programming involves asynchronous data streams. The document explains core FRP concepts like streams and signals. It also introduces RxSwift, a library that brings FRP to iOS. Finally, examples are provided to demonstrate the advantages of using an FRP approach.
Metaprogramming JavaScript
JavaScript allows for metaprogramming through manipulating programs as data. It relies on few but powerful constructs including working with functions, arguments, built-in types, and mechanisms like inheritance at runtime. The key building blocks are objects, numbers, strings, booleans, and undefined, with everything else being objects. Functions are objects that can return other functions, taking advantage of closures to refer to outer variables from inner functions. This flexibility allows for patching implementations, self-optimizing code, custom APIs, and domain-specific languages.
Varnish to the rescue
What is Varnish reverse proxy server, how to configure it, how can it help with day to day problems of a web application.
What's hot (19)
Viewers also liked
RestMQ - HTTP/Redis based Message Queue
RestMQ is a message queue system based on Redis that allows storing and retrieving messages through HTTP requests. It uses Redis' data structures like lists, sets, and hashes to maintain queues and messages. Messages can be added to and received from queues using RESTful endpoints. Additional features include status monitoring, queue control, and support for protocols like JSON, Comet, and WebSockets. The core functionality is language-agnostic but implementations exist in Python and Ruby.
Redis
Redis is a key-value store that provides common data structures like lists, sets, and ordered sets as building blocks. It offers features like asynchronous I/O, fast operations, active development, and different persistence strategies. RestMQ is a message queue built on Redis that uses HTTP, REST, and JSON. It provides COMET consumer functionality and integrates with an asynchronous Redis client and Twisted-based web framework called Cyclone. DOCDB is a prototype document database that indexes documents by tokenizing, removing stop words, stemming words, and grouping them into Redis sets to allow searching by keywords.
NoSQL and SQL Anti Patterns
This document provides examples of common SQL anti-patterns and related NoSQL alternatives. It discusses issues like using tables as trees, caches, queues, or logs. It also addresses dynamic schema/table creation, stored procedures, row padding, complex joins, and object-relational mismatches. The document recommends alternatives like document databases, key-value stores, message brokers, and denormalization. It includes examples of modeling book data in MongoDB and Redis.
Minting Money With Megawatts - How To Mine Bitcoin Profitably (University of ...
Minting money from Megawatts
Bitcoin is a peer-to-peer network for exchanging digital tokens, Bitcoins. Launched in early 2009, there are now 14M of projected 21M Bitcoins in circulation worth $4B in market cap, the annual transaction turnover is $20B.
The Bitcoin network relies on a computationally intensive “hashing” process to clear transactions into the shared transaction ledger, the blockchain, in a process known as mining.
We define a profit function for mining as function of the total network hashrate, miner revenues and technology parameters. Using the profit function, we find the breakeven points, the maximum profitability point, the maximum hashrate and the shortest profitable payback period of the Bitcoin mining network. Finally, we evaluate mining profitability for three generations of Bitcoin mining processors and deployment environments, and predict the future evolution of the mining network.
AnyMQ, Hippie, and the real-time web
The document discusses several technologies for building real-time web applications, including PSGI/Plack, AnyEvent, AnyMQ, AMQP, comet techniques, WebSockets, and Web::Hippie. Specifically, it covers:
- PSGI and Plack for building web applications and middleware in Perl.
- AnyEvent for asynchronous programming and handling connections.
- AnyMQ for message queueing with support for AMQP via plugins.
- Comet techniques like long-polling for server-push capabilities before WebSockets.
- The WebSocket protocol standard and APIs for bidirectional communication.
- Web::Hippie for building real-time web applications in Perl using WebSockets.
You shall not get excited
This document discusses why the author chose to use Erlang for programming. It begins by listing some programming languages and tools to consider. It then discusses the author's experience using Erlang for over 3 years for backend development including REST APIs, data storage, and distributed programs. The author highlights aspects of Erlang like lightweight concurrency, fault tolerance, easy testing and updating of code, and the OTP framework. Some caveats mentioned include carefully using Mnesia for data storage and undocumented features.
How Not To Use The Right Tool For The Wrong Reason
The document discusses the benefits of exercise for mental health. Regular physical activity can help reduce anxiety and depression and improve mood and cognitive function. Exercise causes chemical changes in the brain that may help protect against mental illness and improve symptoms.
Patterns of fail
The document discusses various types of failures in organizations and projects, including failures due to trivial issues that receive disproportionate attention ("bikeshedding"), entrepreneurs who overpromise and underdeliver, and behavioral patterns among team members that can contribute to failure, such as passing blame and not taking responsibility for issues ("chain of irresponsibility"). Specific examples of failures are provided for projects, methodologies, and individuals to illustrate different kinds of failures and how they can be avoided or overcome through learning from mistakes.
Software Instability
The document discusses ensuring software stability in production environments. It emphasizes the importance of non-functional requirements like logging, administrative tools, and monitoring. Tests that simulate real-world failures are also recommended, as well as following architectural best practices for stability. Features should be introduced gradually with on/off switches and thorough testing of upgrades and rollbacks. Overall the document stresses prioritizing stability over new features through practices like timeouts, circuit breakers, and decoupling layers.
Agile or Fragile
The document discusses several challenges that can arise when adopting agile development methods. It describes how operations can become overwhelmed if too many features are released too frequently in short cycles without proper automation or quality assurance testing. It also notes that continuous development should not be an excuse for poorly defined goals or requirements that require reworking the data model or architecture with every iteration. The document provides suggestions for addressing these issues, such as scheduling production releases every 2-3 cycles, focusing on quality assurance, and ensuring development priorities are on the end user experience rather than just completing tasks.
Mapping, Interlinking and Exposing MusicBrainz as Linked Data
Slides from my keynote at the 1st International Workshop on Semantic Music and Media (SMAM2013)
http://iswc2013.semanticweb.org/content/smam-2013
Using puppet, foreman and git to develop and operate a large scale internet s...
This document discusses how eBuddy uses Puppet, Foreman, and Git to develop and operate a large scale internet service. It provides an overview of Puppet for configuration management, Foreman for provisioning nodes and assigning Puppet classes, and how eBuddy uses these tools along with Git and a Kanban process. It also previews plans to automate provisioning fully with Foreman, refactor to Puppet 3.x standards, and implement staged code reviews with Git.
Continuously-Integrated Puppet in a Dynamic Environment
This talk will show how we deploy Puppet without a Puppetmaster on an autoscaling Amazon Web Services infrastructure. Key points of interest: - Masterless Puppet - Use of Jenkins for Puppet manifest testing and environment promotion (test->staging->production) - Puppet integration with Amazon CloudFormation
Sam Bashton
Director, Bashton Ltd
After working for a number of Internet Service Providers, Sam founded Bashton Ltd in 2004. Focussing exclusively on Linux and Open Source software, Sam and his team provide consultancy, support and 24/7 infrastructure management for a number of high-traffic websites. A serial early adopter, Sam has travelled the world providing training and consultancy and generally spreading the Open Source message. Sam lives in Manchester, UK.
JSON and the APInauts
The document discusses API wrappers and why developers create them. Some key points:
- API wrappers provide idiomatic and Ruby-like access to APIs for Ruby developers rather than using raw HTTP requests.
- Wrappers can abstract away a complex API to simplify usage and provide a business domain model.
- Popular Ruby libraries for creating wrappers include HTTParty, RestClient, Weary, and Faraday. These handle HTTP requests and parsing responses.
- Middleware like Hashie and MultiJSON can be used to further Ruby-ify responses.
- Wrappers insulate code from potential API changes and leverage API documentation.
Better encryption & security with MariaDB 10.1 & MySQL 5.7
Talking about the improvements in MariaDB on MySQL security and encryption features that are so important in today's data landscape. Presented http://www.meetup.com/EffectiveMySQL/events/224828891/
Ruby application based on http
The document discusses testing HTTP requests and responses in Ruby. It provides examples of using tools like Wireshark and HTTP Analyzer to capture real HTTP traffic. It then shows how to replay the same requests and validate the responses programmatically in Ruby using libraries like Net::HTTP, Mechanize and FakeWeb. The goal is to test HTTP interactions without relying on the actual backend services.
Sensu
The document discusses switching from Nagios to Sensu for monitoring. Sensu separates concerns better by having specialized tools for each task like alerting vs graphing. Sensu is also more customizable and extensible. Configuration management systems can be used to define checks and subscriptions based on infrastructure roles. Sensu uses a decentralized model where checks are not tied to specific hosts. Checks can be routed to multiple handlers like PagerDuty and Graphite. Converting existing Nagios checks mainly involves updating the configuration management system to scope variables and add checks to roles.
vSphere APIs for performance monitoring
The document discusses vSphere APIs for performance monitoring and provides an overview of useful performance metrics such as CPU, memory, disk, and network. It motivates the need for these APIs by demonstrating how charts and visualizations can help identify performance issues. The agenda covers common useful statistics, how vSphere retrieves performance data, and how to access the data programmatically using tools like PowerCLI and Java/C#.
PostgreSQL Materialized Views with Active Record
How to use PostgreSQL Materialized Views with to simplify code and improve performance of your Ruby on Rails application
The Complete MariaDB Server Tutorial - Percona Live 2015
The document provides an overview of the Complete MariaDB Server Tutorial presentation. It introduces MariaDB and discusses what it is, its goals of being compatible with MySQL and having stable releases. It also covers MariaDB architecture, installation, utilities, and storage engines.
Viewers also liked (20)
Minting Money With Megawatts - How To Mine Bitcoin Profitably (University of ...
Minting Money With Megawatts - How To Mine Bitcoin Profitably (University of ...
How Not To Use The Right Tool For The Wrong Reason
How Not To Use The Right Tool For The Wrong Reason
Mapping, Interlinking and Exposing MusicBrainz as Linked Data
Mapping, Interlinking and Exposing MusicBrainz as Linked Data
Using puppet, foreman and git to develop and operate a large scale internet s...
Using puppet, foreman and git to develop and operate a large scale internet s...
Continuously-Integrated Puppet in a Dynamic Environment
Continuously-Integrated Puppet in a Dynamic Environment
Better encryption & security with MariaDB 10.1 & MySQL 5.7
Better encryption & security with MariaDB 10.1 & MySQL 5.7
The Complete MariaDB Server Tutorial - Percona Live 2015
The Complete MariaDB Server Tutorial - Percona Live 2015
Similar to Dlsecyx pgroammr (Dyslexic Programmer - cool stuff for scaling)
OSCon - Performance vs Scalability
Slides for my talk at OSCon 2011 on scalability vs performance, frameworks for non-blocking I/O and message queues.
Reactive design: languages, and paradigms
A talk first given at React 2014 and refined for YOW! LambdaJam 2014 that explores the meaning of Reactive Programming, as described in the Reactive Manifesto, and how well it is supported by general design paradigms, like Functional Programming, Object-Oriented Programming, and Domain Driven Design, and by particular design approaches, such as Functional Reactive Programming, Reactive Extensions, Actors, etc.
Impedance Mismatch 2.0
The document discusses various approaches to addressing the "impedance mismatch" that occurs when integrating semantic technologies like topic maps with other applications and programming languages. It evaluates approaches like using JSPs directly, writing a custom domain model, generating a domain model from the ontology, and using generic portlet components. While each approach has tradeoffs between flexibility, complexity, and development effort, the document suggests that further work is needed to fully address the impedance mismatch problem between semantic technologies and applications. It invites feedback on the proposed approaches.
How to get started with Site Reliability Engineering
Many companies are looking for "DevOps'' in many forms, but what kind of skills or experiences are actually needed? I’ll debunk some of the myths surrounding what recruiters or internet lurkers might tell you and find out if you might actually have an aptitude for Site Reliability or Infrastructure Engineering. If so, what might be good knowledge areas to get started with? And if learning leads to an interview, what might that look like?
Automate your Job and Business with ChatGPT #3 - Fundamentals of LLM/GPT
This document provides an agenda for a full-day bootcamp on large language models (LLMs) like GPT-3. The bootcamp will cover fundamentals of machine learning and neural networks, the transformer architecture, how LLMs work, and popular LLMs beyond ChatGPT. The agenda includes sessions on LLM strategy and theory, design patterns for LLMs, no-code/code stacks for LLMs, and building a custom chatbot with an LLM and your own data.
Untangling spring week8
This document provides an agenda and overview for a developer training session. It discusses developing a growth mindset for programming, strategies for managing frustration, resources for learning programming concepts and getting help, and approaches for collaborative work. It also introduces backend concepts like servers, databases, and JavaScript on the server side using Node.js. The homework assignment involves researching and documenting programming resources.
Introducing Parallel Pixie Dust
The document introduces Parallel Pixie Dust (PPD), a cross-platform thread library that aims to guarantee deadlock-free and race-condition free schedules that are optimal. It discusses the need for multiple threads due to factors like the memory wall. Current threading models are problematic because testing and debugging threaded code is difficult. PPD uses futures and thread pools to simulate data flow and generate tree-like thread schedules. It provides parallel versions of functions and thread-safe containers to enable multi-threaded standard library algorithms. The goal is to make writing correct multi-threaded programs easier.
Creativity vs Best Practices
This is a presentation I did for the new interns at Duo Software which I highlight the pros and cons of being creative and following widely used best practices in software development
scale_perf_best_practices
The document discusses best practices for scalability and performance when developing PHP applications. Some key points include profiling and optimizing early, cooperating between development and operations teams, testing on production-like data, caching frequently accessed data, avoiding overuse of hard-to-scale resources, and using compiler caching and query optimization. Decoupling applications, caching, data federation, and replication are also presented as techniques for improving scalability.
Le Tour de xUnit
This session showcases several unit testing libraries and frameworks that make it possible to write the most-effective unit and integration tests. It also highlights some of the most underused features of JUnit, including Theories, parameterized tests, and Hamcrest matchers.
Among the libraries it covers: Unitils, Spring Test, DbUnit, XMLUnit, Dumpster, Mockito, and JBehave. The presentation supplies code examples and discusses TDD/BDD best practices.
Better Functional Design through TDD
The document discusses how test-driven development (TDD) can lead to better functional design. It explains that TDD focuses on defining requirements before implementation, limits test and code scope to reduce complexity, and makes dependencies explicit upfront. This helps produce code that is loosely coupled, simple to understand and maintain, and easy to test. The document recommends starting with examples or tests, keeping components small with single responsibilities, and designing dependent parts first.
Feelin' Groovy: An Afternoon of Reflexive Metaprogramming
The document summarizes a presentation about reflexive metaprogramming using the Groovy programming language. It discusses how Groovy supports reflexive metaprogramming through its Meta Object Protocol (MOP) and metaclasses, allowing methods to be dynamically added, removed, or replaced on classes at runtime. It also presents examples of method interception, injection, and synthesis in Groovy and how internal domain-specific languages can be implemented.
Daniel Steigerwald - Este.js - konec velkého Schizma
Vzpomínáte na doby, kdy na všechno stačilo jQuery? Slavme, jsme zpátky v budoucnosti. Svět JavaScriptových knihoven a nástrojů se usadil. Poznejte a naučte se technologie, které následujících minimálně pět let budou mainstreamem. Už není třeba experimentovat, dumat jestli Ember nebo Angular nebo Meteor, odpovědí je React a Flux. Zabaleno a připraveno k použití v produkci v úplně novém Este.js - zero bus factor edition.
Selenium Design Patterns
In this presentation, you will be introduced to Clean Code, Code Smells concepts and anti-patterns in programming, what are the common bad patterns of Selenium code and architectural considerations. We will also go though guidelines on how to write maintainable and reusable automation code, automation of complicated websites, PageObject vs ScreenPlay patterns, and common practices in avoiding and debugging of flaky tests.
Lessons Learned Migrating 2+ Billion Documents at Craigslist
Lessons Learned from Migrating 2+ Billion Documents at Craigslist outlines Craigslist's migration from MySQL to MongoDB. Some key lessons include: knowing your hardware limitations, that replica sets provide high availability during reboots, understanding your data types and sizes, and being aware of limitations with sharding and replica set re-sync processes. The migration addressed issues with their archive data storage and provided a more scalable and performant system.
Semantic web, python, construction industry
This document summarizes a talk given to researchers and those interested in the semantic web. It discusses how Plone can help researchers by automating the creation of prototypes and demos using code generators. It also advocates exposing research data on the semantic web by making it available as XML or RDF files that can be accessed and used by other applications. Examples are given of applications built with Plone that export or import research data to demonstrate how data can be shared and reused.
Six of the Best
The document discusses six programming practices recommended by Kevlin Henney for programmers to follow when working on code. The practices are:
1. Make roots of class hierarchies fully abstract to avoid issues with concrete base classes and increase stability.
2. Inherit for subtyping only to promote understandability and substitutability.
3. Include only what is needed in header files to reduce build time and dependencies.
4. Consider duplicate code a programming error to eliminate bugs and reduce code size.
5. Use self-contained objects to take advantage of C++ features and separation of concerns.
6. Details on the remaining three practices will be covered in the next article.
Concurrent Programming with Ruby and Tuple Spaces
Ruby threads are limited due to the Global Interpreter Lock. Therefore, the best way to do parallel computing with Ruby is to use multiple processes but how do you get these processes to communicate?
This session will provide some strategies for handling multi-process communication in Ruby, with a focus on the use of TupleSpaces. A TupleSpace provides a repository of tuples that can be accessed concurrently to implement a Blackboard system. Ruby ships with a built-in implementation of a TupleSpace with the Rinda library.
During the session, Luc will demonstrate how to use Rinda and will highlight other libraries/projects that facilitate interprocess communication and parallel computing in Ruby.
Low maintenance perl notes
The document discusses optimizing Perl code for easy maintenance. It suggests limiting the programming vocabulary to simpler and more common constructs to make the code easier to read, understand and debug. Specifically, it recommends always using strict and warnings, formatting code consistently with Perltidy, writing code for future readers rather than just oneself, following common conventions when possible, and avoiding obscure, complex or magical language features. It provides examples of features that should generally be avoided, such as formats, punctuation variables and indirect object syntax, to optimize Perl code for long-term maintainability.
Apache Con 2008 Top 10 Mistakes
The document provides tips on common scalability mistakes made when designing web applications and strategies to avoid them. It discusses the importance of considering scalability from the beginning, avoiding blocking calls, caching frequently accessed data, optimizing database and file system usage, and using tools like profilers to identify bottlenecks. The key is designing applications that can scale both up and down based on current needs through a proactive, process-oriented approach.
Similar to Dlsecyx pgroammr (Dyslexic Programmer - cool stuff for scaling) (20)
How to get started with Site Reliability Engineering
How to get started with Site Reliability Engineering
Automate your Job and Business with ChatGPT #3 - Fundamentals of LLM/GPT
Automate your Job and Business with ChatGPT #3 - Fundamentals of LLM/GPT
Feelin' Groovy: An Afternoon of Reflexive Metaprogramming
Feelin' Groovy: An Afternoon of Reflexive Metaprogramming
Daniel Steigerwald - Este.js - konec velkého Schizma
Daniel Steigerwald - Este.js - konec velkého Schizma
Lessons Learned Migrating 2+ Billion Documents at Craigslist
Lessons Learned Migrating 2+ Billion Documents at Craigslist
More from Gleicon Moraes
Como arquiteturas de dados quebram
O documento discute as quebras de arquiteturas de dados, incluindo por design inadequado, falta de capacidade ou dono. Também aborda a gravidade dos dados e casos de arquiteturas que quebraram, como um cluster de banco de dados que cresceu muito rápido sem planejamento.
Arquitetura emergente - sobre cultura devops
Apresentação feita no Sete Masters da iMasters dia 28/07/2016
http://setemasters.imasters.com.br/edicoes/devops/
API Gateway report
This document provides an overview of API gateways. It discusses the API gateway pattern which includes separating client and server code, providing distinct API views from the same origin, and composing calls between APIs. It also includes an architecture diagram and discusses core features like uniform authentication, REST over HTTPS, horizontal scalability, payload rewrite, request composition, and backend as a service. Popular API gateway players like APIGEE, AWS API Gateway, and Kong are compared. Potential pitfalls around dependency, lock-in, scalability, and backend savings are also covered. The conclusion recommends using API gateways as accelerators but planning to reduce their footprint, using standard protocols, managing cache/data, and being able to migrate to an open
DNAD 2015 - Como a arquitetura emergente de sua aplicação pode jogar contra ...
O documento discute os desafios da entrega contínua à medida que sistemas crescem em complexidade. Apresenta falácias comuns em sistemas distribuídos e como requisitos não funcionais são esquecidos, levando a problemas. Sugere focar em métricas, testes robustos, cache, banco de dados e introdução segura de novas features para evitar problemas.
QCon SP 2015 - Advogados do diabo: como a arquitetura emergente de sua aplica...
Este documento discute os desafios de entrega contínua em sistemas complexos reais. Ele destaca como as pressões por novas funcionalidades e mudanças frequentes podem levar a arquiteturas frágeis e mal testadas, dificultando a automação e a entrega contínua. Também enfatiza a importância de métricas, logs, testes abrangentes e padrões como circuit breaker para tornar os sistemas mais robustos e previsíveis.
Por trás da infraestrutura do Cloud - Campus Party 2014
This document discusses infrastructure as a service (IaaS) cloud computing models. It defines IaaS according to NIST and Wikipedia as allowing consumers to provision processing, storage, networks and other computing resources to deploy and run arbitrary software. The consumer does not manage the underlying infrastructure directly but has control over operating systems and applications. Common IaaS resources include virtual machines, storage, networking and security services. The document also discusses common cloud computing building blocks like compute, storage, networking and management services.
Locaweb cloud and sdn
This document discusses Infrastructure as a Service (IaaS) and Software Defined Networking (SDN).
IaaS allows consumers to provision computing resources like servers, storage, and networking and deploy their own operating systems and applications. The consumer does not manage the underlying cloud infrastructure. SDN abstracts traditional network equipment by separating the control and data planes, using a centralized controller and open standards like OpenFlow. This allows network configuration through software instead of dedicated hardware. The document then provides examples of how IaaS resources and SDN architecture could be implemented in a cloud computing environment.
A closer look to locaweb IaaS
This document provides an overview of Locaweb's Infrastructure as a Service (IaaS) engineering team and capabilities. It discusses the team size and responsibilities, defines IaaS, describes Locaweb's IaaS architecture including virtual/physical servers, open source software used, provisioning processes, and resource monitoring. It also lists several open source projects developed by Locaweb to support their IaaS operations.
Semi Automatic Sentiment Analysis
Web 2.0 applications for social networking provide data about users’ mood and opinions in almost real time. Many applications are taking advantage of these data to derive business intelligence. However, the volume of data makes it hard and error-prone to classify sentiments and opinions manually. The combination of data mining techniques and a pipeline to process data from Web 2.0 applications, such as Twitter, Facebook, and Wordpress, makes it possible to apply natural language processing and machine learning techniques to automate partially this task. Therefore, the amount of manual classification is reduced, as the incoming data has already a classification tag that can be easily changed, feeding back the classifier. There is room for improvements and a Brazilian Portuguese Corpus was created to do the initial training of the classifier. The code used for this testing was based on open source libraries and is available as a test bed for different corpora and new algorithms.
L'esprit de l'escalier
Este documento discute os benefícios de usar bancos de dados NoSQL e apresenta vários estudos de caso de empresas que migraram com sucesso para sistemas NoSQL como MongoDB e Redis. Ele também aborda desafios comuns como importação e exportação de dados, recuperação em caso de falha e questões de escalabilidade.
Architectural Anti Patterns - Notes on Data Distribution and Handling Failures
The document discusses several architectural anti-patterns related to data distribution and handling failures when using relational database management systems (RDBMS). It describes anti-patterns such as using tables as caches, queues, log files, or for dynamic schema creation. It also discusses abusing RDBMS features like stored procedures and triggers for application logic as well as using tables for distributed locking. The document is presented as a slide deck covering these anti-patterns to avoid when designing distributed systems that use RDBMS for data storage and access.
Architectural anti-patterns for data handling
This document discusses architectural anti-patterns related to data distribution and handling failures. It provides examples of anti-patterns when using SQL and NoSQL databases, including using tables as queues, logs, or caches instead of the proper tools. Alternatives are suggested such as using message queues, document databases, and key-value stores instead of forcing data models. The document advises to simplify data schemes, avoid over-engineering, and think about how to best structure data and applications.
Architectural anti patterns_for_data_handling
This document discusses architectural anti-patterns related to data distribution and handling failures. It describes issues like using tables for queues, logs, or caches instead of the proper tools. Alternatives presented include document databases, key-value stores, message queues, and avoiding over-normalization. The document advocates simplifying data models and thinking about architecture and data flow rather than only databases.
NoSql Introduction
NoSQL presentation at Locaweb/Brazil.
Basic ideas, anti-patterns and some ideas of when/how to jump to NoSQL solutions.
More from Gleicon Moraes (14)
DNAD 2015 - Como a arquitetura emergente de sua aplicação pode jogar contra ...
DNAD 2015 - Como a arquitetura emergente de sua aplicação pode jogar contra ...
QCon SP 2015 - Advogados do diabo: como a arquitetura emergente de sua aplica...
QCon SP 2015 - Advogados do diabo: como a arquitetura emergente de sua aplica...
Por trás da infraestrutura do Cloud - Campus Party 2014
Por trás da infraestrutura do Cloud - Campus Party 2014
Architectural Anti Patterns - Notes on Data Distribution and Handling Failures
Architectural Anti Patterns - Notes on Data Distribution and Handling Failures
Recently uploaded
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Dmitrii Kamaev, PhD
Senior Product Owner - QIAGEN
QA or the Highway - Component Testing: Bridging the gap between frontend appl...
These are the slides for the presentation, "Component Testing: Bridging the gap between frontend applications" that was presented at QA or the Highway 2024 in Columbus, OH by Zachary Hamm.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
Gursev Pirge, PhD
Senior Data Scientist - JohnSnowLabs
JavaLand 2024: Application Development Green Masterplan
My presentation slides I used at JavaLand 2024
"NATO Hackathon Winner: AI-Powered Drug Search", Taras Kloba
This is a session that details how PostgreSQL's features and Azure AI Services can be effectively used to significantly enhance the search functionality in any application.
In this session, we'll share insights on how we used PostgreSQL to facilitate precise searches across multiple fields in our mobile application. The techniques include using LIKE and ILIKE operators and integrating a trigram-based search to handle potential misspellings, thereby increasing the search accuracy.
We'll also discuss how the azure_ai extension on PostgreSQL databases in Azure and Azure AI Services were utilized to create vectors from user input, a feature beneficial when users wish to find specific items based on text prompts. While our application's case study involves a drug search, the techniques and principles shared in this session can be adapted to improve search functionality in a wide range of applications. Join us to learn how PostgreSQL and Azure AI can be harnessed to enhance your application's search capability.
Session 1 - Intro to Robotic Process Automation.pdf
👉 Check out our full 'Africa Series - Automation Student Developers (EN)' page to register for the full program:
https://bit.ly/Automation_Student_Kickstart
In this session, we shall introduce you to the world of automation, the UiPath Platform, and guide you on how to install and setup UiPath Studio on your Windows PC.
📕 Detailed agenda:
What is RPA? Benefits of RPA?
RPA Applications
The UiPath End-to-End Automation Platform
UiPath Studio CE Installation and Setup
💻 Extra training through UiPath Academy:
Introduction to Automation
UiPath Business Automation Platform
Explore automation development with UiPath Studio
👉 Register here for our upcoming Session 2 on June 20: Introduction to UiPath Studio Fundamentals: https://community.uipath.com/events/details/uipath-lagos-presents-session-2-introduction-to-uipath-studio-fundamentals/
"What does it really mean for your system to be available, or how to define w...
We will talk about system monitoring from a few different angles. We will start by covering the basics, then discuss SLOs, how to define them, and why understanding the business well is crucial for success in this exercise.
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications."$10 thousand per minute of downtime: architecture, queues, streaming and fin...
Direct losses from downtime in 1 minute = $5-$10 thousand dollars. Reputation is priceless.
As part of the talk, we will consider the architectural strategies necessary for the development of highly loaded fintech solutions. We will focus on using queues and streaming to efficiently work and manage large amounts of data in real-time and to minimize latency.
We will focus special attention on the architectural patterns used in the design of the fintech system, microservices and event-driven architecture, which ensure scalability, fault tolerance, and consistency of the entire system.
Northern Engraving | Nameplate Manufacturing Process - 2024
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
Principle of conventional tomography-Bibash Shahi ppt..pptx
before the computed tomography, it had been widely used.
Dandelion Hashtable: beyond billion requests per second on a commodity server
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Apps Break Data
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
AppSec PNW: Android and iOS Application Security with MobSF
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
Must Know Postgres Extension for DBA and Developer during Migration
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
Twitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
Facebook(Meta): https://www.facebook.com/mydbops/
ScyllaDB Tablets: Rethinking Replication
ScyllaDB is making a major architecture shift. We’re moving from vNode replication to tablets – fragments of tables that are distributed independently, enabling dynamic data distribution and extreme elasticity. In this keynote, ScyllaDB co-founder and CTO Avi Kivity explains the reason for this shift, provides a look at the implementation and roadmap, and shares how this shift benefits ScyllaDB users.
Recently uploaded (20)
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
QA or the Highway - Component Testing: Bridging the gap between frontend appl...
QA or the Highway - Component Testing: Bridging the gap between frontend appl...
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
Harnessing the Power of NLP and Knowledge Graphs for Opioid Research
JavaLand 2024: Application Development Green Masterplan
JavaLand 2024: Application Development Green Masterplan
"NATO Hackathon Winner: AI-Powered Drug Search", Taras Kloba
"NATO Hackathon Winner: AI-Powered Drug Search", Taras Kloba
Session 1 - Intro to Robotic Process Automation.pdf
Session 1 - Intro to Robotic Process Automation.pdf
"What does it really mean for your system to be available, or how to define w...
"What does it really mean for your system to be available, or how to define w...
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
"$10 thousand per minute of downtime: architecture, queues, streaming and fin...
"$10 thousand per minute of downtime: architecture, queues, streaming and fin...
Northern Engraving | Nameplate Manufacturing Process - 2024
Northern Engraving | Nameplate Manufacturing Process - 2024
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Principle of conventional tomography-Bibash Shahi ppt..pptx
Principle of conventional tomography-Bibash Shahi ppt..pptx
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
AppSec PNW: Android and iOS Application Security with MobSF
AppSec PNW: Android and iOS Application Security with MobSF
Must Know Postgres Extension for DBA and Developer during Migration
Must Know Postgres Extension for DBA and Developer during Migration
Dlsecyx pgroammr (Dyslexic Programmer - cool stuff for scaling)
- 1. Dlsiecyx Pgroeammr The cool stuff for scaling
- 3. Disclaimer about me - I like both Ruby and Python, but I dislike the generator/deferred model they implement for non-blocking I/O - I think node.js beats them because its better wrapped, as EM synchrony does to EM and gevent for python. - I don't think this model is mandatory, not even migrate from Blocking to non-blocking I/O is needed for most cases. The best solution may not lie in code complexity. Maybe the right architecture. - I like Erlang, the actor/message passing model and pattern matching. Way more. And I like message queues. Specially this one: http://www.restmq.com
- 4. Disclaimer about dyslexia From wikipedia (http://en.wikipedia.org/wiki/Dyslexia): "... Many students reach higher education before they encounter the threshold at which they are no longer able to compensate for their learning weaknesses. One common misconception about dyslexia is that dyslexic readers write words backwards or move letters around when reading. In fact, this only occurs in a very small population of dyslexic readers. Dyslexic people are better identified by writing that does not seem to match their level of intelligence from prior observations. Additionally, dyslexic people often substitute similar-looking, but unrelated, words in place of the ones intended (what/want, say/saw, help/held, run/fun, fell/fall, to/too, etc.)"
- 5. Basics Asynchronous I/O - Posix aio_* Non-Blocking I/O Select, Poll, EPoll, KQueue Evented I/O - Abstraction over any I/O Model Reactor - Pattern for multiplexing I/O Future Programming Generator Deferred Event Emitters The c10k problem - http://www.kegel.com/c10k. html
- 7. Scalability, not Performance 1. Performance: same work with less effort 2. Scalability: more work with more resources 3. Scientific measures for performance: How much and How fast 4. Tricks to improve performance can hurt scalability. e.g: Map/Reduce is scalable, not fast (not suited for real time queries) 5. Non-Blocking I/O is not an optimization for Performance 6. The time spent waiting for an external resource can be used to other tasks, given a known introduced complexity in the code. 7. Most of time architectural changes can avoid deeper code changes (1,2,3,4 - Goetz et al, Java Concurrency in Practice, M/R example is mine) (5,6,7 - Lucindo, R. http://slidesha.re/aYz4Mk, wording on 6 is mine)
- 8. Wait, Wat ?
- 10. Ruby Python
- 12. URL Fetch Benchmark 2 urls Sequential blocking I/O using ruby: 0m3.061s Non-blocking I/O using ruby and Eventmachine: 0m0.795s 28 urls Sequential blocking I/O using ruby: 0m56.014s Non-blocking I/O using ruby and Eventmachine: 0m24.519s
- 14. Python/Twisted
- 15. Python/Twisted - Verbose and Inlined
- 19. Python/Twisted - Inline Callbacks
- 21. Python/gevent
- 22. Python/gevent - monkey patch
- 23. Python/gevent - join the greenlets
- 29. Ruby/EventMachine/EM-Synchrony - Fiber based
- 30. Node.js
- 31. Node.js
- 32. Node.js - Creating and ending the Request
- 33. Node.js - Event handlers
- 35. Erlang
- 36. Erlang - Spawning a process to each URL
- 37. Erlang - Single URL download
- 38. Reminder of what we wanted to do
- 39. Ruby Python
- 41. Decoupling db writes with Message Queues
- 42. Coupled comment
- 43. Uncoupled comment - producer
- 44. Uncoupled comment - consumer
- 45. Cache
- 46. HTML processing - no cache http://github.com/gleicon/vuvuzelr/proxy_no_cache.rb
- 47. HTML processing - Cached http://github.com/gleicon/vuvuzelr/proxy.rb