際際滷shows by User: MaxNeunhffer / http://www.slideshare.net/images/logo.gif 際際滷shows by User: MaxNeunhffer / Fri, 26 Feb 2016 08:13:28 GMT 際際滷Share feed for 際際滷shows by User: MaxNeunhffer Deep Dive on ArangoDB /slideshow/deep-dive-on-arangodb/58745353 deepdivearangodb-160226081328
We will take a deep dive into ArangoDB (https://www.arangodb.com/) together with Max (https://www.linkedin.com/in/maxneunhoeffer) one of the core developers of the product. ArangoDB is a multi-model database, which means that it is a document store, a key/value store and a graph database, all in one engine and with a query language that supports all three data models, as well as joins and transactions. Queries can use a single data model or can even mix them. ArangoDB scales out horizontally with convenient cluster deployment using Apache Mesos. Furthermore, the HTTP API can easily be extended by server-side JavaScript code using high performance access to the C++ database core. During the talk I will show all these features using several different cloud deployments, since in most projects one will not deploy a ArangoDB monolith, but rather multiple instances, each either a possibly replicated single server, or a cluster. This demonstrates that all these properties together make ArangoDB a very useful and valuable tool in modern microservice oriented architectures.]]>
We will take a deep dive into ArangoDB (https://www.arangodb.com/) together with Max (https://www.linkedin.com/in/maxneunhoeffer) one of the core developers of the product. ArangoDB is a multi-model database, which means that it is a document store, a key/value store and a graph database, all in one engine and with a query language that supports all three data models, as well as joins and transactions. Queries can use a single data model or can even mix them. ArangoDB scales out horizontally with convenient cluster deployment using Apache Mesos. Furthermore, the HTTP API can easily be extended by server-side JavaScript code using high performance access to the C++ database core. During the talk I will show all these features using several different cloud deployments, since in most projects one will not deploy a ArangoDB monolith, but rather multiple instances, each either a possibly replicated single server, or a cluster. This demonstrates that all these properties together make ArangoDB a very useful and valuable tool in modern microservice oriented architectures.]]> Fri, 26 Feb 2016 08:13:28 GMT /slideshow/deep-dive-on-arangodb/58745353 MaxNeunhffer@slideshare.net(MaxNeunhffer) Deep Dive on ArangoDB MaxNeunhffer We will take a deep dive into ArangoDB (https://www.arangodb.com/) together with Max (https://www.linkedin.com/in/maxneunhoeffer) one of the core developers of the product. ArangoDB is a multi-model database, which means that it is a document store, a key/value store and a graph database, all in one engine and with a query language that supports all three data models, as well as joins and transactions. Queries can use a single data model or can even mix them. ArangoDB scales out horizontally with convenient cluster deployment using Apache Mesos. Furthermore, the HTTP API can easily be extended by server-side JavaScript code using high performance access to the C++ database core. During the talk I will show all these features using several different cloud deployments, since in most projects one will not deploy a ArangoDB monolith, but rather multiple instances, each either a possibly replicated single server, or a cluster. This demonstrates that all these properties together make ArangoDB a very useful and valuable tool in modern microservice oriented architectures. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/deepdivearangodb-160226081328-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> We will take a deep dive into ArangoDB (https://www.arangodb.com/) together with Max (https://www.linkedin.com/in/maxneunhoeffer) one of the core developers of the product. ArangoDB is a multi-model database, which means that it is a document store, a key/value store and a graph database, all in one engine and with a query language that supports all three data models, as well as joins and transactions. Queries can use a single data model or can even mix them. ArangoDB scales out horizontally with convenient cluster deployment using Apache Mesos. Furthermore, the HTTP API can easily be extended by server-side JavaScript code using high performance access to the C++ database core. During the talk I will show all these features using several different cloud deployments, since in most projects one will not deploy a ArangoDB monolith, but rather multiple instances, each either a possibly replicated single server, or a cluster. This demonstrates that all these properties together make ArangoDB a very useful and valuable tool in modern microservice oriented architectures.
Deep Dive on ArangoDB from Max Neunhffer
]]> 3144 5 https://cdn.slidesharecdn.com/ss_thumbnails/deepdivearangodb-160226081328-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 Scaling ArangoDB on Mesosphere DCOS /slideshow/scaling-arangodb-on-mesosphere-dcos/53478128 mesosmeetuphamburg-151002203551-lva1-app6891
Recently, ArangoDB integrated its cluster management with Apache Mesos. This makes it now possible to launch an ArangoDB cluster on a Mesos cluster with a single, albeit complex shell command. In a DCOS-enabled Mesosphere cluster this is even easier, because one can use the dcos subcommand for ArangoDB, which essentially turns a Mesosphere cluster into a single, large computer. In this talk I explain the whole setup and show (live on stage) how to deploy ArangoDB clusters on Amazon Web Services, and how we used this to scale ArangoDB up until it could sustain 1000000 document writes per second.]]>
Recently, ArangoDB integrated its cluster management with Apache Mesos. This makes it now possible to launch an ArangoDB cluster on a Mesos cluster with a single, albeit complex shell command. In a DCOS-enabled Mesosphere cluster this is even easier, because one can use the dcos subcommand for ArangoDB, which essentially turns a Mesosphere cluster into a single, large computer. In this talk I explain the whole setup and show (live on stage) how to deploy ArangoDB clusters on Amazon Web Services, and how we used this to scale ArangoDB up until it could sustain 1000000 document writes per second.]]> Fri, 02 Oct 2015 20:35:51 GMT /slideshow/scaling-arangodb-on-mesosphere-dcos/53478128 MaxNeunhffer@slideshare.net(MaxNeunhffer) Scaling ArangoDB on Mesosphere DCOS MaxNeunhffer Recently, ArangoDB integrated its cluster management with Apache Mesos. This makes it now possible to launch an ArangoDB cluster on a Mesos cluster with a single, albeit complex shell command. In a DCOS-enabled Mesosphere cluster this is even easier, because one can use the dcos subcommand for ArangoDB, which essentially turns a Mesosphere cluster into a single, large computer. In this talk I explain the whole setup and show (live on stage) how to deploy ArangoDB clusters on Amazon Web Services, and how we used this to scale ArangoDB up until it could sustain 1000000 document writes per second. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/mesosmeetuphamburg-151002203551-lva1-app6891-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Recently, ArangoDB integrated its cluster management with Apache Mesos. This makes it now possible to launch an ArangoDB cluster on a Mesos cluster with a single, albeit complex shell command. In a DCOS-enabled Mesosphere cluster this is even easier, because one can use the dcos subcommand for ArangoDB, which essentially turns a Mesosphere cluster into a single, large computer. In this talk I explain the whole setup and show (live on stage) how to deploy ArangoDB clusters on Amazon Web Services, and how we used this to scale ArangoDB up until it could sustain 1000000 document writes per second.
Scaling ArangoDB on Mesosphere DCOS from Max Neunhffer
]]> 1049 7 https://cdn.slidesharecdn.com/ss_thumbnails/mesosmeetuphamburg-151002203551-lva1-app6891-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Scaling ArangoDB on Mesosphere DCOS /slideshow/scaling-arangodb-on-mesosphere/52382378 nosqlusergroup2015-150903130550-lva1-app6892
Recently, ArangoDB integrated its cluster management with Apache Mesos. This makes it now possible to launch an ArangoDB cluster on a Mesos cluster with a single, albeit complex shell command. In a DCOS-enabled Mesosphere cluster this is even easier, because one can use the dcos subcommand for ArangoDB, which essentially turns a Mesosphere cluster into a single, large computer. In this talk I explain the whole setup and show (live on stage) how to deploy ArangoDB clusters on Google Compute Engine, and how we used this to scale ArangoDB up until it could sustain 1000000 document writes per second.]]>
Recently, ArangoDB integrated its cluster management with Apache Mesos. This makes it now possible to launch an ArangoDB cluster on a Mesos cluster with a single, albeit complex shell command. In a DCOS-enabled Mesosphere cluster this is even easier, because one can use the dcos subcommand for ArangoDB, which essentially turns a Mesosphere cluster into a single, large computer. In this talk I explain the whole setup and show (live on stage) how to deploy ArangoDB clusters on Google Compute Engine, and how we used this to scale ArangoDB up until it could sustain 1000000 document writes per second.]]> Thu, 03 Sep 2015 13:05:50 GMT /slideshow/scaling-arangodb-on-mesosphere/52382378 MaxNeunhffer@slideshare.net(MaxNeunhffer) Scaling ArangoDB on Mesosphere DCOS MaxNeunhffer Recently, ArangoDB integrated its cluster management with Apache Mesos. This makes it now possible to launch an ArangoDB cluster on a Mesos cluster with a single, albeit complex shell command. In a DCOS-enabled Mesosphere cluster this is even easier, because one can use the dcos subcommand for ArangoDB, which essentially turns a Mesosphere cluster into a single, large computer. In this talk I explain the whole setup and show (live on stage) how to deploy ArangoDB clusters on Google Compute Engine, and how we used this to scale ArangoDB up until it could sustain 1000000 document writes per second. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/nosqlusergroup2015-150903130550-lva1-app6892-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Recently, ArangoDB integrated its cluster management with Apache Mesos. This makes it now possible to launch an ArangoDB cluster on a Mesos cluster with a single, albeit complex shell command. In a DCOS-enabled Mesosphere cluster this is even easier, because one can use the dcos subcommand for ArangoDB, which essentially turns a Mesosphere cluster into a single, large computer. In this talk I explain the whole setup and show (live on stage) how to deploy ArangoDB clusters on Google Compute Engine, and how we used this to scale ArangoDB up until it could sustain 1000000 document writes per second.
Scaling ArangoDB on Mesosphere DCOS from Max Neunhffer
]]> 978 7 https://cdn.slidesharecdn.com/ss_thumbnails/nosqlusergroup2015-150903130550-lva1-app6892-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 Processing large-scale graphs with Google Pregel /slideshow/pregel-46324168/46324168 pregel-150326105951-conversion-gate01
Graphs are a very popular data structure to store relations like friendship or web pages and their links. Therefore graph databases have become popular recently and some of them even allow sharding, i.e. automatic distribution of the data across multiple machines. On the other hand, very computation-intensive algorithms for graphs are known and used in practice, and they often access very large data sets, which leads to heavy communication loads. Therefore, it is an obvious idea to run such graph algorithms on the database servers, close to the data, making use of the computational power of the storage nodes. Google's Pregel framework allows to implement a lot of graph algorithms in a general system and plays a role similar to the map-reduce skeleton, but for graphs. In this talk I will explain the framework and describe its implementation in the multi-model database ArangoDB.]]>
Graphs are a very popular data structure to store relations like friendship or web pages and their links. Therefore graph databases have become popular recently and some of them even allow sharding, i.e. automatic distribution of the data across multiple machines. On the other hand, very computation-intensive algorithms for graphs are known and used in practice, and they often access very large data sets, which leads to heavy communication loads. Therefore, it is an obvious idea to run such graph algorithms on the database servers, close to the data, making use of the computational power of the storage nodes. Google's Pregel framework allows to implement a lot of graph algorithms in a general system and plays a role similar to the map-reduce skeleton, but for graphs. In this talk I will explain the framework and describe its implementation in the multi-model database ArangoDB.]]> Thu, 26 Mar 2015 10:59:49 GMT /slideshow/pregel-46324168/46324168 MaxNeunhffer@slideshare.net(MaxNeunhffer) Processing large-scale graphs with Google Pregel MaxNeunhffer Graphs are a very popular data structure to store relations like friendship or web pages and their links. Therefore graph databases have become popular recently and some of them even allow sharding, i.e. automatic distribution of the data across multiple machines. On the other hand, very computation-intensive algorithms for graphs are known and used in practice, and they often access very large data sets, which leads to heavy communication loads. Therefore, it is an obvious idea to run such graph algorithms on the database servers, close to the data, making use of the computational power of the storage nodes. Google's Pregel framework allows to implement a lot of graph algorithms in a general system and plays a role similar to the map-reduce skeleton, but for graphs. In this talk I will explain the framework and describe its implementation in the multi-model database ArangoDB. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/pregel-150326105951-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Graphs are a very popular data structure to store relations like friendship or web pages and their links. Therefore graph databases have become popular recently and some of them even allow sharding, i.e. automatic distribution of the data across multiple machines. On the other hand, very computation-intensive algorithms for graphs are known and used in practice, and they often access very large data sets, which leads to heavy communication loads. Therefore, it is an obvious idea to run such graph algorithms on the database servers, close to the data, making use of the computational power of the storage nodes. Google&#39;s Pregel framework allows to implement a lot of graph algorithms in a general system and plays a role similar to the map-reduce skeleton, but for graphs. In this talk I will explain the framework and describe its implementation in the multi-model database ArangoDB.
Processing large-scale graphs with Google Pregel from Max Neunhffer
]]> 1664 1 https://cdn.slidesharecdn.com/ss_thumbnails/pregel-150326105951-conversion-gate01-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 Multi-model databases and node.js /slideshow/bay-node-multimodel/46184318 baynodemultimodel-150323133738-conversion-gate01
In this talk I will explain the motivation behind the multi model database approach, discuss its advantages and limitations, and will keep the presentation concrete and practice oriented by showing concrete usage examples from node.js .]]>
In this talk I will explain the motivation behind the multi model database approach, discuss its advantages and limitations, and will keep the presentation concrete and practice oriented by showing concrete usage examples from node.js .]]> Mon, 23 Mar 2015 13:37:37 GMT /slideshow/bay-node-multimodel/46184318 MaxNeunhffer@slideshare.net(MaxNeunhffer) Multi-model databases and node.js MaxNeunhffer In this talk I will explain the motivation behind the multi model database approach, discuss its advantages and limitations, and will keep the presentation concrete and practice oriented by showing concrete usage examples from node.js . <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/baynodemultimodel-150323133738-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> In this talk I will explain the motivation behind the multi model database approach, discuss its advantages and limitations, and will keep the presentation concrete and practice oriented by showing concrete usage examples from node.js .
Multi-model databases and node.js from Max Neunhffer
]]> 2090 1 https://cdn.slidesharecdn.com/ss_thumbnails/baynodemultimodel-150323133738-conversion-gate01-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 Backbone using Extensible Database APIs over HTTP /MaxNeunhffer/extensible-backbonesfextensible-database-apis-and-their-role-in-software-architecture extensiblebackbonesf-150323132104-conversion-gate01
These days, more and more software applications are designed using a micro services architecture, that is, as suites of independently deployable services, talking to each other with well-defined interfaces. This approach is helped by the fact that many NoSQL databases expose their API through HTTP, which makes it particularly easy to define the interfaces. The multi-model NoSQL database ArangoDB embeds Google's V8 JavaScript engine and features the Foxx framework, which allows the developer to extend ArangoDB's API by user defined JavaScript code that runs on the database server. In this talk I will explain the benefits of this approach to the software architecture and development process. I will keep the presentation practice oriented by showing concrete examples in ArangoDB and JavaScript, using Backbone.js ]]>
These days, more and more software applications are designed using a micro services architecture, that is, as suites of independently deployable services, talking to each other with well-defined interfaces. This approach is helped by the fact that many NoSQL databases expose their API through HTTP, which makes it particularly easy to define the interfaces. The multi-model NoSQL database ArangoDB embeds Google's V8 JavaScript engine and features the Foxx framework, which allows the developer to extend ArangoDB's API by user defined JavaScript code that runs on the database server. In this talk I will explain the benefits of this approach to the software architecture and development process. I will keep the presentation practice oriented by showing concrete examples in ArangoDB and JavaScript, using Backbone.js ]]> Mon, 23 Mar 2015 13:21:03 GMT /MaxNeunhffer/extensible-backbonesfextensible-database-apis-and-their-role-in-software-architecture MaxNeunhffer@slideshare.net(MaxNeunhffer) Backbone using Extensible Database APIs over HTTP MaxNeunhffer These days, more and more software applications are designed using a micro services architecture, that is, as suites of independently deployable services, talking to each other with well-defined interfaces. This approach is helped by the fact that many NoSQL databases expose their API through HTTP, which makes it particularly easy to define the interfaces. The multi-model NoSQL database ArangoDB embeds Google's V8 JavaScript engine and features the Foxx framework, which allows the developer to extend ArangoDB's API by user defined JavaScript code that runs on the database server. In this talk I will explain the benefits of this approach to the software architecture and development process. I will keep the presentation practice oriented by showing concrete examples in ArangoDB and JavaScript, using Backbone.js <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/extensiblebackbonesf-150323132104-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> These days, more and more software applications are designed using a micro services architecture, that is, as suites of independently deployable services, talking to each other with well-defined interfaces. This approach is helped by the fact that many NoSQL databases expose their API through HTTP, which makes it particularly easy to define the interfaces. The multi-model NoSQL database ArangoDB embeds Google&#39;s V8 JavaScript engine and features the Foxx framework, which allows the developer to extend ArangoDB&#39;s API by user defined JavaScript code that runs on the database server. In this talk I will explain the benefits of this approach to the software architecture and development process. I will keep the presentation practice oriented by showing concrete examples in ArangoDB and JavaScript, using Backbone.js
Backbone using Extensible Database APIs over HTTP from Max Neunhffer
]]> 1043 1 https://cdn.slidesharecdn.com/ss_thumbnails/extensiblebackbonesf-150323132104-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Complex queries in a distributed multi-model database /slideshow/tech-talkgeekdom/45962190 techtalkgeekdom-150317174601-conversion-gate01
A multi-model database is a document store, a graph database as well as a key/value store. To allow for convenient and powerful querying such a database needs a query language that understands all three data models and allows to mix these models in queries. For example, it should be possible to find some documents in a collection according to some criteria, then follow some edges in a graph in which the documents represent vertices, and finally join the results with documents from yet another collection. In this talk I will explain how a query engine for such a language works, give an overview of the life of a query from parsing, over translation into an execution plan, the optimisation phase and finally the execution. I will show how distributed query execution plans look like, how the query optimiser reasons about them and how the distributed execution works.]]>
A multi-model database is a document store, a graph database as well as a key/value store. To allow for convenient and powerful querying such a database needs a query language that understands all three data models and allows to mix these models in queries. For example, it should be possible to find some documents in a collection according to some criteria, then follow some edges in a graph in which the documents represent vertices, and finally join the results with documents from yet another collection. In this talk I will explain how a query engine for such a language works, give an overview of the life of a query from parsing, over translation into an execution plan, the optimisation phase and finally the execution. I will show how distributed query execution plans look like, how the query optimiser reasons about them and how the distributed execution works.]]> Tue, 17 Mar 2015 17:46:00 GMT /slideshow/tech-talkgeekdom/45962190 MaxNeunhffer@slideshare.net(MaxNeunhffer) Complex queries in a distributed multi-model database MaxNeunhffer A multi-model database is a document store, a graph database as well as a key/value store. To allow for convenient and powerful querying such a database needs a query language that understands all three data models and allows to mix these models in queries. For example, it should be possible to find some documents in a collection according to some criteria, then follow some edges in a graph in which the documents represent vertices, and finally join the results with documents from yet another collection. In this talk I will explain how a query engine for such a language works, give an overview of the life of a query from parsing, over translation into an execution plan, the optimisation phase and finally the execution. I will show how distributed query execution plans look like, how the query optimiser reasons about them and how the distributed execution works. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/techtalkgeekdom-150317174601-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> A multi-model database is a document store, a graph database as well as a key/value store. To allow for convenient and powerful querying such a database needs a query language that understands all three data models and allows to mix these models in queries. For example, it should be possible to find some documents in a collection according to some criteria, then follow some edges in a graph in which the documents represent vertices, and finally join the results with documents from yet another collection. In this talk I will explain how a query engine for such a language works, give an overview of the life of a query from parsing, over translation into an execution plan, the optimisation phase and finally the execution. I will show how distributed query execution plans look like, how the query optimiser reasons about them and how the distributed execution works.
Complex queries in a distributed multi-model database from Max Neunhffer
]]> 1040 1 https://cdn.slidesharecdn.com/ss_thumbnails/techtalkgeekdom-150317174601-conversion-gate01-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 Overhauling a database engine in 2 months /slideshow/sf-move-fastbreakthings/45805574 sfmovefastbreakthings-150313112511-conversion-gate01
In 2014 we had to do a major overhaul of ArangoDB's database engine,because we wanted to introduce a write-ahead log. Since for a database this change is similar in nature to the proverbial open-heart surgery for humans, it was clear from day one that this would be a difficult endeavour with a lot of risk to break things. Rather fundamental changes were needed in nearly all places of the kernel code and it seemedimpossible to serialise the work to keep the system in a working state. As usual, time was at a premium, since the next major release had to go out of the door in 2 months time. In this talk I will tell the story of this overhaul, explain the role of unit tests and continuous integration and describe the challenges we faced and how finally overcame them.]]>
In 2014 we had to do a major overhaul of ArangoDB's database engine,because we wanted to introduce a write-ahead log. Since for a database this change is similar in nature to the proverbial open-heart surgery for humans, it was clear from day one that this would be a difficult endeavour with a lot of risk to break things. Rather fundamental changes were needed in nearly all places of the kernel code and it seemedimpossible to serialise the work to keep the system in a working state. As usual, time was at a premium, since the next major release had to go out of the door in 2 months time. In this talk I will tell the story of this overhaul, explain the role of unit tests and continuous integration and describe the challenges we faced and how finally overcame them.]]> Fri, 13 Mar 2015 11:25:11 GMT /slideshow/sf-move-fastbreakthings/45805574 MaxNeunhffer@slideshare.net(MaxNeunhffer) Overhauling a database engine in 2 months MaxNeunhffer In 2014 we had to do a major overhaul of ArangoDB's database engine,because we wanted to introduce a write-ahead log. Since for a database this change is similar in nature to the proverbial open-heart surgery for humans, it was clear from day one that this would be a difficult endeavour with a lot of risk to break things. Rather fundamental changes were needed in nearly all places of the kernel code and it seemedimpossible to serialise the work to keep the system in a working state. As usual, time was at a premium, since the next major release had to go out of the door in 2 months time. In this talk I will tell the story of this overhaul, explain the role of unit tests and continuous integration and describe the challenges we faced and how finally overcame them. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/sfmovefastbreakthings-150313112511-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> In 2014 we had to do a major overhaul of ArangoDB&#39;s database engine,because we wanted to introduce a write-ahead log. Since for a database this change is similar in nature to the proverbial open-heart surgery for humans, it was clear from day one that this would be a difficult endeavour with a lot of risk to break things. Rather fundamental changes were needed in nearly all places of the kernel code and it seemedimpossible to serialise the work to keep the system in a working state. As usual, time was at a premium, since the next major release had to go out of the door in 2 months time. In this talk I will tell the story of this overhaul, explain the role of unit tests and continuous integration and describe the challenges we faced and how finally overcame them.
Overhauling a database engine in 2 months from Max Neunhffer
]]> 1167 4 https://cdn.slidesharecdn.com/ss_thumbnails/sfmovefastbreakthings-150313112511-conversion-gate01-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 Experience with C++11 in ArangoDB /slideshow/sf-accu-2015/45767563 sfaccu2015-150312135340-conversion-gate01
ArangoDB is an open source, multi-model NoSQL database that is written in C++ and embeds Google's V8 engine to implement the higher levels of its functionality in JavaScript. Recently we decided to switch from C++03 to C++11 for the database kernel. In this talk I will first give a short overview of the software architecture of ArangoDB and proceed to tell you about our practical experiences with the switch to C++11. I will explain which of the parts of the "new" standard have been more important and which have been less useful, and I will report about the difficulties we encountered.]]>
ArangoDB is an open source, multi-model NoSQL database that is written in C++ and embeds Google's V8 engine to implement the higher levels of its functionality in JavaScript. Recently we decided to switch from C++03 to C++11 for the database kernel. In this talk I will first give a short overview of the software architecture of ArangoDB and proceed to tell you about our practical experiences with the switch to C++11. I will explain which of the parts of the "new" standard have been more important and which have been less useful, and I will report about the difficulties we encountered.]]> Thu, 12 Mar 2015 13:53:39 GMT /slideshow/sf-accu-2015/45767563 MaxNeunhffer@slideshare.net(MaxNeunhffer) Experience with C++11 in ArangoDB MaxNeunhffer ArangoDB is an open source, multi-model NoSQL database that is written in C++ and embeds Google's V8 engine to implement the higher levels of its functionality in JavaScript. Recently we decided to switch from C++03 to C++11 for the database kernel. In this talk I will first give a short overview of the software architecture of ArangoDB and proceed to tell you about our practical experiences with the switch to C++11. I will explain which of the parts of the "new" standard have been more important and which have been less useful, and I will report about the difficulties we encountered. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/sfaccu2015-150312135340-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> ArangoDB is an open source, multi-model NoSQL database that is written in C++ and embeds Google&#39;s V8 engine to implement the higher levels of its functionality in JavaScript. Recently we decided to switch from C++03 to C++11 for the database kernel. In this talk I will first give a short overview of the software architecture of ArangoDB and proceed to tell you about our practical experiences with the switch to C++11. I will explain which of the parts of the &quot;new&quot; standard have been more important and which have been less useful, and I will report about the difficulties we encountered.
Experience with C++11 in ArangoDB from Max Neunhffer
]]> 1866 3 https://cdn.slidesharecdn.com/ss_thumbnails/sfaccu2015-150312135340-conversion-gate01-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 guacamole: an Object Document Mapper for ArangoDB /slideshow/guacamole-an-object-document-mapper-for-arangodb/45530558 rubyrailssf2015-150306133512-conversion-gate01
In this talk I will give a brief introduction and overview for guacamole, showing how easy it is to get started with using ArangoDB as the persistence layer for a Rails app. I will also explain the philosophy behind ArangoDB's "multi-model approach", but still show concrete code examples, and all of this in 15 minutes.]]>
In this talk I will give a brief introduction and overview for guacamole, showing how easy it is to get started with using ArangoDB as the persistence layer for a Rails app. I will also explain the philosophy behind ArangoDB's "multi-model approach", but still show concrete code examples, and all of this in 15 minutes.]]> Fri, 06 Mar 2015 13:35:12 GMT /slideshow/guacamole-an-object-document-mapper-for-arangodb/45530558 MaxNeunhffer@slideshare.net(MaxNeunhffer) guacamole: an Object Document Mapper for ArangoDB MaxNeunhffer In this talk I will give a brief introduction and overview for guacamole, showing how easy it is to get started with using ArangoDB as the persistence layer for a Rails app. I will also explain the philosophy behind ArangoDB's "multi-model approach", but still show concrete code examples, and all of this in 15 minutes. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/rubyrailssf2015-150306133512-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> In this talk I will give a brief introduction and overview for guacamole, showing how easy it is to get started with using ArangoDB as the persistence layer for a Rails app. I will also explain the philosophy behind ArangoDB&#39;s &quot;multi-model approach&quot;, but still show concrete code examples, and all of this in 15 minutes.
guacamole: an Object Document Mapper for ArangoDB from Max Neunhffer
]]> 1397 1 https://cdn.slidesharecdn.com/ss_thumbnails/rubyrailssf2015-150306133512-conversion-gate01-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 Extensible Database APIs and their role in Software Architecture /slideshow/extensible-sf2015/45530425 extensiblesf2015-150306133103-conversion-gate01
This event will start with a presentation on Extensible database APIs and their role in software architecture, centered around JavaScript. This will be followed by a hands-on interactive workshop. Participants with their own computers will learn how to create a small web application with a database backend, within the session, using only JavaScript. This will be a guided hands-on session using the multi-model NoSQL database ArangoDB and its Foxx JavaScript extension framework. Presenting this workshop will be Max Neunh旦ffer from https://www.arangodb.com/.]]>
This event will start with a presentation on Extensible database APIs and their role in software architecture, centered around JavaScript. This will be followed by a hands-on interactive workshop. Participants with their own computers will learn how to create a small web application with a database backend, within the session, using only JavaScript. This will be a guided hands-on session using the multi-model NoSQL database ArangoDB and its Foxx JavaScript extension framework. Presenting this workshop will be Max Neunh旦ffer from https://www.arangodb.com/.]]> Fri, 06 Mar 2015 13:31:03 GMT /slideshow/extensible-sf2015/45530425 MaxNeunhffer@slideshare.net(MaxNeunhffer) Extensible Database APIs and their role in Software Architecture MaxNeunhffer This event will start with a presentation on Extensible database APIs and their role in software architecture, centered around JavaScript. This will be followed by a hands-on interactive workshop. Participants with their own computers will learn how to create a small web application with a database backend, within the session, using only JavaScript. This will be a guided hands-on session using the multi-model NoSQL database ArangoDB and its Foxx JavaScript extension framework. Presenting this workshop will be Max Neunh旦ffer from https://www.arangodb.com/. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/extensiblesf2015-150306133103-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> This event will start with a presentation on Extensible database APIs and their role in software architecture, centered around JavaScript. This will be followed by a hands-on interactive workshop. Participants with their own computers will learn how to create a small web application with a database backend, within the session, using only JavaScript. This will be a guided hands-on session using the multi-model NoSQL database ArangoDB and its Foxx JavaScript extension framework. Presenting this workshop will be Max Neunh旦ffer from https://www.arangodb.com/.
Extensible Database APIs and their role in Software Architecture from Max Neunhffer
]]> 1127 1 https://cdn.slidesharecdn.com/ss_thumbnails/extensiblesf2015-150306133103-conversion-gate01-thumbnail.jpg?width=120&height=120&fit=bounds presentation White http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Is multi-model the future of NoSQL? /slideshow/future-nosql2015/45529774 futurenosql2015-150306131107-conversion-gate01
Recently a new breed of "multi-model" databases has emerged. They are a document store, a graph database and a key/value store combined in one program. Therefore they are able to cover a lot of use cases which otherwise would need multiple different database systems. This approach promises a boost to the idea of "polyglot persistence", which has become very popular in recent years although it creates some friction in the form of data conversion and synchronisation between different systems. This is, because with a multi-model database one can enjoy the benefits of polyglot persistence without the disadvantages. In this talk I will explain the motivation behind the multi-model approach, discuss its advantages and limitations, and will then risk to make some predictions about the NoSQL database market in five years time, which I shall only reveal during the talk.]]>
Recently a new breed of "multi-model" databases has emerged. They are a document store, a graph database and a key/value store combined in one program. Therefore they are able to cover a lot of use cases which otherwise would need multiple different database systems. This approach promises a boost to the idea of "polyglot persistence", which has become very popular in recent years although it creates some friction in the form of data conversion and synchronisation between different systems. This is, because with a multi-model database one can enjoy the benefits of polyglot persistence without the disadvantages. In this talk I will explain the motivation behind the multi-model approach, discuss its advantages and limitations, and will then risk to make some predictions about the NoSQL database market in five years time, which I shall only reveal during the talk.]]> Fri, 06 Mar 2015 13:11:06 GMT /slideshow/future-nosql2015/45529774 MaxNeunhffer@slideshare.net(MaxNeunhffer) Is multi-model the future of NoSQL? MaxNeunhffer Recently a new breed of "multi-model" databases has emerged. They are a document store, a graph database and a key/value store combined in one program. Therefore they are able to cover a lot of use cases which otherwise would need multiple different database systems. This approach promises a boost to the idea of "polyglot persistence", which has become very popular in recent years although it creates some friction in the form of data conversion and synchronisation between different systems. This is, because with a multi-model database one can enjoy the benefits of polyglot persistence without the disadvantages. In this talk I will explain the motivation behind the multi-model approach, discuss its advantages and limitations, and will then risk to make some predictions about the NoSQL database market in five years time, which I shall only reveal during the talk. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/futurenosql2015-150306131107-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Recently a new breed of &quot;multi-model&quot; databases has emerged. They are a document store, a graph database and a key/value store combined in one program. Therefore they are able to cover a lot of use cases which otherwise would need multiple different database systems. This approach promises a boost to the idea of &quot;polyglot persistence&quot;, which has become very popular in recent years although it creates some friction in the form of data conversion and synchronisation between different systems. This is, because with a multi-model database one can enjoy the benefits of polyglot persistence without the disadvantages. In this talk I will explain the motivation behind the multi-model approach, discuss its advantages and limitations, and will then risk to make some predictions about the NoSQL database market in five years time, which I shall only reveal during the talk.
Is multi-model the future of NoSQL? from Max Neunhffer
]]> 1336 1 https://cdn.slidesharecdn.com/ss_thumbnails/futurenosql2015-150306131107-conversion-gate01-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 Oslo bekk2014 /slideshow/oslo-bekk2014/42264283 oslobekk2014-141202094634-conversion-gate01
]]>
]]> Tue, 02 Dec 2014 09:46:34 GMT /slideshow/oslo-bekk2014/42264283 MaxNeunhffer@slideshare.net(MaxNeunhffer) Oslo bekk2014 MaxNeunhffer <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/oslobekk2014-141202094634-conversion-gate01-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br>
Oslo bekk2014 from Max Neunhffer
]]> 404 2 https://cdn.slidesharecdn.com/ss_thumbnails/oslobekk2014-141202094634-conversion-gate01-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 Oslo baksia2014 /MaxNeunhffer/oslo-baksia2014 oslobaksia2014-141202094246-conversion-gate02
Domain Driven Design is a software development process that focuses on finding a common language for the involved parties. This language and the resulting models are taken from the domain rather than the technical details of the implementation. The goal is to improve the communication between customers, developers and all other involved groups. Even if Eric Evan's book about this topic was written almost ten years ago, this topic remains important because a lot of projects fail for communication reasons. Relational databases have their own language and influence the design of software into a direction further away from the Domain: Entities have to be created for the sole purpose of adhering to best practices of relational database. Two kinds of NoSQL databases are changing that: Document stores and graph databases. In a document store you can model a "contains" relation in a more natural way and thereby express if this entity can exist outside of its surrounding entity. A graph database allows you to model relationships between entities in a straight forward way that can be expressed in the language of the domain. In this talk I want to look at the way a multi model database that combines a document store and a graph database can help you to model your problems in a way that is understandable for all parties involved, and explain the benefits of this approach for the software development process.]]>
Domain Driven Design is a software development process that focuses on finding a common language for the involved parties. This language and the resulting models are taken from the domain rather than the technical details of the implementation. The goal is to improve the communication between customers, developers and all other involved groups. Even if Eric Evan's book about this topic was written almost ten years ago, this topic remains important because a lot of projects fail for communication reasons. Relational databases have their own language and influence the design of software into a direction further away from the Domain: Entities have to be created for the sole purpose of adhering to best practices of relational database. Two kinds of NoSQL databases are changing that: Document stores and graph databases. In a document store you can model a "contains" relation in a more natural way and thereby express if this entity can exist outside of its surrounding entity. A graph database allows you to model relationships between entities in a straight forward way that can be expressed in the language of the domain. In this talk I want to look at the way a multi model database that combines a document store and a graph database can help you to model your problems in a way that is understandable for all parties involved, and explain the benefits of this approach for the software development process.]]> Tue, 02 Dec 2014 09:42:46 GMT /MaxNeunhffer/oslo-baksia2014 MaxNeunhffer@slideshare.net(MaxNeunhffer) Oslo baksia2014 MaxNeunhffer Domain Driven Design is a software development process that focuses on finding a common language for the involved parties. This language and the resulting models are taken from the domain rather than the technical details of the implementation. The goal is to improve the communication between customers, developers and all other involved groups. Even if Eric Evan's book about this topic was written almost ten years ago, this topic remains important because a lot of projects fail for communication reasons. Relational databases have their own language and influence the design of software into a direction further away from the Domain: Entities have to be created for the sole purpose of adhering to best practices of relational database. Two kinds of NoSQL databases are changing that: Document stores and graph databases. In a document store you can model a "contains" relation in a more natural way and thereby express if this entity can exist outside of its surrounding entity. A graph database allows you to model relationships between entities in a straight forward way that can be expressed in the language of the domain. In this talk I want to look at the way a multi model database that combines a document store and a graph database can help you to model your problems in a way that is understandable for all parties involved, and explain the benefits of this approach for the software development process. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/oslobaksia2014-141202094246-conversion-gate02-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Domain Driven Design is a software development process that focuses on finding a common language for the involved parties. This language and the resulting models are taken from the domain rather than the technical details of the implementation. The goal is to improve the communication between customers, developers and all other involved groups. Even if Eric Evan&#39;s book about this topic was written almost ten years ago, this topic remains important because a lot of projects fail for communication reasons. Relational databases have their own language and influence the design of software into a direction further away from the Domain: Entities have to be created for the sole purpose of adhering to best practices of relational database. Two kinds of NoSQL databases are changing that: Document stores and graph databases. In a document store you can model a &quot;contains&quot; relation in a more natural way and thereby express if this entity can exist outside of its surrounding entity. A graph database allows you to model relationships between entities in a straight forward way that can be expressed in the language of the domain. In this talk I want to look at the way a multi model database that combines a document store and a graph database can help you to model your problems in a way that is understandable for all parties involved, and explain the benefits of this approach for the software development process.
Oslo baksia2014 from Max Neunhffer
]]> 442 1 https://cdn.slidesharecdn.com/ss_thumbnails/oslobaksia2014-141202094246-conversion-gate02-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-MaxNeunhffer-48x48.jpg?cb=1535554760 https://www.arangodb.com https://cdn.slidesharecdn.com/ss_thumbnails/deepdivearangodb-160226081328-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/deep-dive-on-arangodb/58745353 Deep Dive on ArangoDB https://cdn.slidesharecdn.com/ss_thumbnails/mesosmeetuphamburg-151002203551-lva1-app6891-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/scaling-arangodb-on-mesosphere-dcos/53478128 Scaling ArangoDB on Me... https://cdn.slidesharecdn.com/ss_thumbnails/nosqlusergroup2015-150903130550-lva1-app6892-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/scaling-arangodb-on-mesosphere/52382378 Scaling ArangoDB on Me...