Talk by Paul Rayner (http://thepaulrayner.com/about/)
https://dddeurope.com/2016/paul-rayner.html
Key things to keep in mind :
- Inevitable - you do or not, good or bad, concisely or unconsciously
| class SayHello extends React.Component { | |
| constructor(props) { | |
| super(props); | |
| this.state = {message: 'Hello!'}; | |
| // This line is important! | |
| this.handleClick = this.handleClick.bind(this); | |
| } | |
| handleClick() { | |
| alert(this.state.message); |
| import React, { Component } from 'react'; | |
| import * as BooksAPI from './BooksAPI'; | |
| import ShelfComponent from './ShelfComponent'; | |
| class App extends Component { | |
| state = { | |
| books: [] | |
| } | |
| componentDidMount(){ | |
| BooksAPI.getAll().then(booksfromServer=> this.setState({books:booksfromServer})) |
| const race = '100m Dash'; | |
| const winners = ['Hunter Gath', 'Singa Song', 'Imda Bos']; | |
| const win = winners.map((winner, i) => ({name: winner, race, place: i + 1})); | |
| const ages = [23,62,45,234,2,62,234,62,34]; | |
| const old = ages.filter(age => age >= 60); | |
| console.log(old); | |
| const names = ['wes', 'kait', 'lux']; |
| // A Declarative Pipeline is defined within a 'pipeline' block. | |
| pipeline { | |
| // agent defines where the pipeline will run. | |
| agent { | |
| // This also could have been 'agent any' - that has the same meaning. | |
| label "" | |
| // Other possible built-in agent types are 'agent none', for not running the | |
| // top-level on any agent (which results in you needing to specify agents on | |
| // each stage and do explicit checkouts of scm in those stages), 'docker', |
| Verifying my Blockstack ID is secured with the address 18XMQA5Tama91EXeRuYLnyuU5Jd6oTYXhw https://explorer.blockstack.org/address/18XMQA5Tama91EXeRuYLnyuU5Jd6oTYXhw |
Talk by Paul Rayner (http://thepaulrayner.com/about/)
https://dddeurope.com/2016/paul-rayner.html
Key things to keep in mind :
Use below command to convert certificate format
3 main areas to address
Data controller or processor - activities ( roles of various participants )
| On Neo4J Desktop browser console : | |
| To connect to the graph | |
| - Connect:play http://guides.neo4j.com/modeling_sandbox/05_refactoring_large_graphs.html | |
| Steps: | |
| - As our graph gets bigger in size it starts to become unfeasible to refactor the whole thing in one go. Instead we’ll have to update it in batches. | |
| Manual batching | |
| When batching we sacrifice the atomicity that we’d get if we did everything in one transaction. It’s therefore useful to make our refactoring queries idempotent in case we need to re-run them. We also need to decide which node we’re going to center the refactoring around. |
| Topic | N Tier | Web-Queue-Worker | Microservices | Event-driven architecture