(文章来源于：鸡窝在线天使投行）

FA在投资界，其意思为财务顾问，英语Financial Advisor的 缩写，别名”新型投资银行“，其核心作用是为企业融资提供第三方的专业服务。财务顾问在企业融资和发展的过程中，起到了举足轻重的作用。像京东、聚美优品都成长过程中，基本都有专业化的FA在服务。FA绝对不是到处发小广告一样的拉皮条，真正靠谱的FA甚至要比投资经理更懂得投资。

客观来说，财务顾问在国内资本行业中的口碑一般，这个游走于投资者与企业之间的群体的天然使命应当为消除交易双方信息不对称，像有人说过“其实自己没钱，但是因为他们的专业性，认识的VC、PE和投行的人多，他们帮助你从外面找钱，从这一点来说有点像拉皮条的”。

但是，真正靠谱的FA，还是需要两把刷子的。

FA 的价值

专业的FA可以提供有针对性的服务。FA了解主流投资机构的口味与风格，可以实现最优匹配；以自身的信誉做背书，企业能够接触到投资机构决策层；引荐几家不同的投资机构，有利于交易条件谈判；同时，以FA出面来撮合交易，可以在很大程度上避免销售过度（Overshopped）的形象，有利于融资成功。

· 帮你梳理融资的故事

1）分析市场上有哪些可比项目有哪些，现在都是什么阶段了；

2）发觉、提炼项目的优势，同时用投资人的语言更好的表现出来。

3） 为项目融资规划提出专业化的建议，比如何时融资应该何时，第一轮对二轮融资多少合适，估值该定多少。

· 帮你对接合适的投资人

1） 介绍最可能理解你的机构和机构里面合适的项目经理，减少鸡同鸭讲的概率；

2）作为第三方斡旋，促进沟通。

· 帮你从头至尾协调从协议到交割的所有流程

1） 作为一名知心姐姐在你在屡战屡败的投资人哪里，舒缓你的情绪，给予信心；

2）对投资合同谈判提出专业化的建议。

啥为伪FA

对投资行业缺少基本的认识，不了解投资人的工作方式和偏好。接到项目后就满大街的散发。如果发现你的BP在各种群、论坛里流传，就要小心遇到伪FA咯。 你想想，大街上叫唤的卖奢侈品的你会信吗？

收取高额的前期费用。业界专业的FA是后期收费的， 帮你融资前不会收取费用的，因为在接单的时候，他就有很大把握可以融到资了。当然，专业的FA，对项目也会有严格的尽调，把握很小的项目不轻易接。可想而知，如果你作为FA推给投资人的都是那些所谓世界独一无二的项目，长了投资人还会看你的邮件吗？

如何鉴别真假FA

其实很简单问几个问题就了解了：

1、让他列出前50强哪些机构不会看我们的项目（前50强机构对投资阶段、投资行业还是有比较大的区分，里面有多家细分行业和阶段的）

2、从可能对我们感兴趣的机构中，随机挑选两家，让他给你分析下内部随会适合看我们的项目。然后让他给你看看他与这个机构的人是否有日常的联系和沟通。

尤其是对于首次融资的创业者们，鉴别这些不靠谱的FA的最佳方式，就是在投资人提出要对你DD之前，先跟其他投资圈里的人、他所服务过的公司DD一下你眼前的投资人。

Src:http://www.badrit.com/blog/2013/11/18/redis-vs-mongodb-performance#.VY2-qROqpBc

MongoDB is an open source document database, and the leading NoSQL database which is written in C++ and Redis is also an open source NoSQL database but it is key-value store rather than document database. Redis is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets.

Here’s a simple benchmark in node.js to compare the performance between Redis and MongoDB. The benchmark compares the time of writing and reading for both. For Redis I used node.js Redis client and for MongoDB I used node.js MongoDB driver

And here’s the code

In case of redis:

var redis = require("redis") 
,	client = redis.createClient() 
,	numberOfElements = 50000; 

client.del({},function(err,reply){ 
	redisWrite(); 
}); 

function redisWrite () { 
 console.time('redisWrite'); 
   for (var i = 0; i < numberOfElements; i++) { 
	 client.set(i, "some fantastic value " + i,function(err,data){ 
	   if (--i === 0) { 
	       console.timeEnd('redisWrite'); 
	       redisRead(); 
	       } 
	 }); 
   }; 
} 

function redisRead(){ 
 client = redis.createClient(); 
 console.time('redisRead'); 
 for (var i = 0; i < numberOfElements; i++) { 
       client.get(i, function (err, reply) { 
         if (--i === 0) { 
	     console.timeEnd('redisRead'); 
	     } 
       }); 
 } 
}

In case of MongoDB:

var MongoClient = require('mongodb').MongoClient 
, numberOfElements=50000;    

MongoClient.connect('mongodb://127.0.0.1:27017/test', function(err, db) { 
   var collection = db.collection('benchmark'); 
   collection.ensureIndex({id:1},{} ,console.log); 
   collection.remove({}, function(err) { // to remove any element from the database at first 
   mongoWrite(collection,db); 
   }); 
}) 

function mongoWrite(collection,db){ 
  console.time('mongoWrite'); 
  for (var i = 0; i < numberOfElements; i++) { 
        collection.insert({id:i,value:"some fantastic value " + i}, function(err, docs) { 
          if(--i==0){ 
             console.timeEnd('mongoWrite'); 
             mongoRead(collection,db); 
          }      
        }); 
  }; 
} 


function mongoRead(collection,db){ 
 console.time('mongoRead'); 
 for (var i = 0; i < numberOfElements; i++) { 
       collection.findOne({id:i},function(err, results) { 
         if(--i==0){ 
            console.timeEnd('mongoRead'); 
            db.close(); 
            } 
       }); 
 } 
}

Results were measured using MongoDB 2.4.8 and Redis 2.6.16

Machine Specifications

• Processor : 4x Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz
• Memory : 3892MB
• Operating System : Ubuntu 13.04
• Kernel -Version : Linux 3.8.0-33-generic (x86_64)

Calculated time in milliseconds (lower is better)

Form results we can see that both Mongo and Redis have almost equal time in case of small number of entries but when this number increases, Redis has remarkable superiority over mongo.

The results will vary according to your programming language and also according to the specifications of your machine.

The Servlet 4.0 specification is out and Tomcat 9.0.x will support it. However, at this point Tomcat 8.0.x is the best Tomcat version and it is supporting the 3.1 Servlet Spec.

Since OS X 10.7 Java is not (pre-)installed anymore, let’s fix that first.

Prerequisite: Java

As I’m writing this, Java 8u45 is the latest version, available for download here: http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

The JDK installer package come in an dmg and installs easily on the Mac; and after opening the Terminal app again,

java -version

now shows something like this:

java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)

Whatever you do, when opening Terminal and running java -version, you should see something like this, with a version of at least 1.7.x I.e. Tomcat 8.x requires Java 7 or later.

JAVA_HOME is an important environment variable, not just for Tomcat, and it’s important to get it right. Here is a trick that allows me to keep the environment variable current, even after a Java Update was installed. In ~/.bash_profile, I set the variable like so:

export JAVA_HOME=$(/usr/libexec/java_home)

Installing Tomcat

Here are the easy to follow steps to get it up and running on your Mac

1. Download a binary distribution of the core module: apache-tomcat-8.0.22.tar.gz from here. I picked the tar.gz in Binary Distributions / Core section.
2. Opening/unarchiving the archive will create a folder structure in your Downloads folder: (btw, this free Unarchiver app is perfect for all kinds of compressed files and superior to the built-in Archive Utility.app)
   ~/Downloads/apache-tomcat-8.0.22
3. Open to Terminal app to move the unarchived distribution to /usr/local
   sudo mkdir -p /usr/local
sudo mv ~/Downloads/apache-tomcat-8.0.22 /usr/local
4. To make it easy to replace this release with future releases, we are going to create a symbolic link that we are going to use when referring to Tomcat (after removing the old link, you might have from installing a previous version):
   sudo rm -f /Library/Tomcat
sudo ln -s /usr/local/apache-tomcat-8.0.22 /Library/Tomcat

5. Change ownership of the /Library/Tomcat folder hierarchy:
   sudo chown -R <your_username> /Library/Tomcat
6. Make all scripts executable:
   sudo chmod +x /Library/Tomcat/bin/*.sh

Instead of using the start and stop scripts, like so:

47 wolf:~$ /Library/Tomcat/bin/startup.sh
Using CATALINA_BASE: /Library/Tomcat
Using CATALINA_HOME: /Library/Tomcat
Using CATALINA_TMPDIR: /Library/Tomcat/temp
Using JRE_HOME: /Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home
Using CLASSPATH: /Library/Tomcat/bin/bootstrap.jar:/Library/Tomcat/bin/tomcat-juli.jar
Tomcat started.
48 wolf:~$ /Library/Tomcat/bin/shutdown.sh
Using CATALINA_BASE: /Library/Tomcat
Using CATALINA_HOME: /Library/Tomcat
Using CATALINA_TMPDIR: /Library/Tomcat/temp
Using JRE_HOME: /Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home
Using CLASSPATH: /Library/Tomcat/bin/bootstrap.jar:/Library/Tomcat/bin/tomcat-juli.jar
49 wolf:~$

you may also want to check out Activata’s Tomcat Controller, a tiny freeware app, providing a UI to quickly start/stop Tomcat. It may not say so, but Tomcat Controller works on OS X 10.10 just fine.

Finally, after your started Tomcat, open your Mac’s Web browser and take a look at the default page: http://localhost:8080

Reference: https://wolfpaulus.com/jounal/mac/tomcat8/

This tutorial will walk you through setting up a user on your MySQL server to connect remotely.

The following items are assumed:

• You have access to login as the ‘root’ MySQL user

Getting your IP address

You will need to know what the IP address you are connecting from. To find this you can go to one of the following sites:

• http://www.ipchicken.com
• http://www.whatismyip.com

Granting Access

Granting access to a user from a remote host is fairly simple and can be accomplished from just a few steps. First you will need to login to your MySQL server as the root user. You can do this by typing the following command:

# mysql -u root -p

This will prompt you for your MySQL root password.

Once you are logged into MySQL you need to issue the GRANT command that will enable access for your remote user. In this example we will be creating a brand new user (fooUser) that will have full access to the fooDatabase database.

Keep in mind that this statement is not complete and will need some items changed. Please change 1.2.3.4 to the IP address that we obtained above. You will also need to change my_password with the password that you would like to use for fooUser.

mysql> GRANT ALL ON fooDatabase.* TO fooUser@'1.2.3.4' IDENTIFIED BY 'my_password';

This statement will grant ALL permissions to the newly created user fooUser with a password of ‘my_password’ when they connect from the IP address 1.2.3.4.

Testing Remotely

Now you can test your connection remotely. You can access your MySQL server from another Linux server:

# mysql -u fooUser -p -h 44.55.66.77
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 17
Server version: 5.0.45 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> _

Note that the IP of our MySQL server is 44.55.66.77 in this example.

Notes

There are a few things to note when setting up these remote users:

• When setting up users a local user is not the same thing as a remote user. For instance fooUser@localhost is not the same as fooUser@1.2.3.4. You will have to duplicate permissions if you want them to have the same permissions.
• Granting ALL permissions is not advised. Using GRANT SELECT,INSERT,UPDATE,DELETE is a wise alternative for a normal user.
• If you would like to grant only to a specific table you can use database.table instead of database.*. In respect to our example above you could put fooDatabase.fooTable.
• If you are using iptables you will need to make an entry in your firewall for TCP port 3306. When creating your firewall rule you can simply use the name ‘mysql’ for the port number. Search our wiki for iptables and you will find a list of common rule sets which include an entry for MySQL.

Reference:

https://www.rackspace.com/knowledge_center/article/mysql-connect-to-your-database-remotely

http://www.cyberciti.biz/tips/how-do-i-enable-remote-access-to-mysql-database-server.html