Skip to main content

Posts

Showing posts from September, 2017

RESTful Web services: The basic - IBM Developer Work

© Copyright IBM Corporation 2008, 2015 Trademarks RESTful Web services: The basics Page 1 of 10 RESTful Web services: The basics Alex Rodriguez  ( arodrigu@us.ibm.com ) Software Engineer IBM 09 February 2015 (First published 06 November 2008) Representational State Transfer (REST) has gained widespread acceptance across the Web as a simpler alternative to SOAP- and Web Services Description Language (WSDL)-based Web services. Key evidence of this shift in interface design is the adoption of REST by mainstream Web 2.0 service providers—including Yahoo, Google, and Facebook—who have deprecated or passed on SOAP and WSDL-based interfaces in favor of an easier-to-use, resource-oriented model to expose their services. In this article, Alex Rodriguez introduces you to the basic principles of REST. REST defines a set of architectural principles by which you can design Web services that focus on a system's resources, including how resource states are addressed and transferred o

Build vs Buy 2

When all the features needed by the users at a given customer are available one could consider this a success. The users have their requirements met and the software vendor has a model that works for them. Unfortunately, there is a problem: All those features that are present in the software but that are not needed by a given user add overhead for the customer and their users. First and foremost, the features are visible and at best may just take up space in menus, toolbars, etc but at worst may confuse the users or make use of required features more complicated. This often translates to lost productivity and increased training effort. The additional features are also likely to result in a higher resource usage, such as memory and storage space as well as network utilisation, which translates into higher capital expenditure for hardware and increased operational costs. https://www.thoughtworks.com/insights/blog/buy-versus-build-shift-issues-buying-software An extreme case is Micros

Install, config GitLab on Ubuntu 16.04

http://blog.cloud66.com/installing-gitlab-ubuntu/ https://stackoverflow.com/questions/31762841/how-to-serve-other-vhosts-next-to-gitlab-omnibus-server-full-step-by-step-solu GitLab like Redmine use ruby source code. So to run with nginx we need phusion passenger. Run gitlab alongside with many another web (PHP, NodeJS). We need install git, ruby, recompile nginx with phusion passenger. Nginx do not load runtime lib like .so or binary. Install nodejs. Access database (PostgreSQL)sudo -u gitlab-psql /opt/gitlab/embedded/bin/psql -h /var/opt/gitlab/postgresql/ gitlabhq_production Here about 100 tables for gitlab. So long from the last time I use postgres :(. gitlabhq_production=# \dt                          List of relations  Schema |                   Name                   | Type  | Owner   --------+------------------------------------------+-------+--------  public | abuse_reports                            | table | gitlab  public | appearances                      

Thought Work 17 Sept

https://www.sandimetz.com/blog/2017/9/13/breaking-up-the-behemoth Churn - new measure unit/way. Complex and frequently changed code (git commits). Complex but rarely change code may be OK. Not complex but changed frequently also be OK. OO vs complex (big) procedural code. OO is cost-effective.... https://www.kitchensoap.com/2017/08/12/multiple-perspectives-on-technical-problems-and-solutions/  Architecture Review Working Group, or “ARWG” was developed. The main idea was that such a group could keep the practice going without senior engineering leadership bringing an authoritarian flavor to the meetings, and continually model the behavior the practice needed to encourage the multiple perspectives that departures needed. You might be thinking: “but where and when does a decision   get made?” The ARWG’s role was  not  to make a decision. The ARWG’s role was to  create and sustain the conditions where a dialogue can take place , with as many perspectives on both the proble

Epress authen, routing, middleware ...

https://stackoverflow.com/questions/11784233/using-passportjs-how-does-one-pass-additional-form-fields-to-the-local-authenti https://blog.risingstack.com/node-hero-node-js-authentication-passport-js/ https://www.owasp.org/index.php/Session_Management_Cheat_Sheet https://stackoverflow.com/questions/10306185/nodejs-best-way-to-pass-common-variables-into-separate-modules https://www.npmjs.com/package/express-passport-session-tracker https://stackoverflow.com/questions/16800418/how-to-properly-pass-mysql-connection-to-routes-with-express-js https://scotch.io/tutorials/easy-node-authentication-setup-and-local https://scotch.io/bar-talk/the-ins-and-outs-of-token-based-authentication https://scotch.io/tutorials/the-anatomy-of-a-json-web-token https://jonathanmh.com/express-passport-json-web-token-jwt-authentication-beginners/ https://github.com/jaredhanson/passport/blob/master/lib/strategies/session.js https://stackoverflow.com/questions/2015232/database-design-for-audit-