函数式编程是一种编程的范式和编程的方法论(programming paradigm),它属于结构化编程的一种,主要的思想是把运算的过程尽量通过一组嵌套的函数来实现。
函数式编程的几个特点:
函数式编程的优点:
@FunctionalInterface是 Java 8 新加入的一种接口,注解在接口层面,且注解的接口要有且仅有一个抽象方法。具体就是说,注解在Inteface上,且interface里只能有一个抽象方法,可以有多个default方法。
函数式接口的一大特性就是可以被lambda表达式和函数引用表达式代替
Lambda 表达式是一种匿名函数(对 Java 而言这并不完全正确,但现在姑且这么认为),简单地说,它是没有声明的方法,也即没有访问修饰符、返回值声明和名字。
你可以将其想做一种速记,在你需要使用某个方法的地方写上它。当某个方法只使用一次,而且定义很简短,使用这种速记替代之尤其有效,这样,你就不必在类中费力写声明与方法了。
JAVA是面向对象的,通常方法的入参都是类(对象),或者变量,而函数式编程,就是把一个函数(方法)作为入参,那这个有啥好处呢??
简单举个例子,
当多个方法都有同样的操作时,我们通常想的是将其共同抽象成独立方法,但是整个流程是一样的,只是不同场景下,具体业务处理处理不同时,我们该怎么抽象呢?如果像下面那样操作,明显就是破坏了整个业务流程
public Object common1(){return "common1";}public Object common2(){return "common2";}public void method1(Object o){Object o1 =this.common1();//doSomeingSystem.out.println("========"+o1);this.common2();}public void method2(Object o){Object o1 =this.common1();//doSomeingSystem.out.println("-----------"+o1);this.common2();}
那想再不破坏整个流程的情况改怎么处理呢?可以利用函数式编程,把接口作为入参,当具体业务处理时再去实现其具体业务。
@FunctionalInterface
public interface Operation {public T operate(R r);
}public void common(Operation
上面的介绍过于抽象,下面介绍一个很实用的场景。
对于一些池的操作,比如redisPool,或者线程池,都有一些通用的操作,首先,先从池中取出对象,然后实现具体业务,然后再把对象放入池中;
可以看出这里有操作流程上有重复的地方,如果我们把这写都写在具体业务中,过于耦合和繁琐,那我们就可以像上面的demo一样,将其公用部分抽象出来,这里已redisPool为例,如下
@FunctionalInterface
public interface Operation {public T operate(R r);}
public class RedisTool2 {private static final String LOCK_SUCCESS = "OK";private static final Long RELEASE_SUCCESS = 1L;//NX|XX, NX -- Only set the key if it does not already exist;// XX -- Only set the key if it already exist.private static final String SET_IF_NOT_EXIST = "NX";//EX|PX, expire time units: EX = seconds; PX = millisecondsprivate static final String SET_WITH_EXPIRE_TIME = "PX";private static volatile JedisPool jedisPool = null;public static JedisPool getRedisPoolUtil() {if(null == jedisPool ){synchronized (RedisTool2.class){if(null == jedisPool){GenericObjectPoolConfig poolConfig = new GenericObjectPoolConfig();poolConfig.setMaxTotal(100);poolConfig.setMaxIdle(10);poolConfig.setMaxWaitMillis(100*1000);poolConfig.setTestOnBorrow(true);jedisPool = new JedisPool(poolConfig,"192.168.10.151",6379);}}}return jedisPool;}public static T doOperation(Operation operation){Jedis jedis = jedisPool.getResource();try {return operation.operate(jedis);}catch (Exception e){return null;}finally {jedisPool.returnResource(jedis);}}//使用匿名内部类实现public static boolean tryGetDistributedLock1(final String lockKey, final String requestId, final int expireTime) {return doOperation(new Operation() {public Boolean operate(Jedis jedis) {String result = jedis.set(lockKey, requestId, SET_IF_NOT_EXIST, SET_WITH_EXPIRE_TIME, expireTime);if (LOCK_SUCCESS.equals(result)) {return true;}return false;}});}//使用lambda表达式实现public static boolean tryGetDistributedLock2(final String lockKey, final String requestId, final int expireTime) {return doOperation(jedis ->{String result = jedis.set(lockKey, requestId, SET_IF_NOT_EXIST, SET_WITH_EXPIRE_TIME, expireTime);if (LOCK_SUCCESS.equals(result)) {return true;}return false;});}//使用lambda表达式实现public static boolean tryGetDistributedLock2(final String lockKey, final String requestId, final int expireTime) {String result = doOperation(jedis ->jedis.set(lockKey, requestId, SET_IF_NOT_EXIST,SET_WITH_EXPIRE_TIME, expireTime));return LOCK_SUCCESS.equals(result);}public boolean releaseDistributedLock(String lockKey, String requestId) {String script = "if redis.call('get', KEYS[1]) == ARGV[1] then return redis.call('del', KEYS[1]) else return 0 end";Object result = this.execute(jedis ->jedis.eval(script, Collections.singletonList(COMMON_LOCK_KEY+lockKey), Collections.singletonList(requestId)));return RELEASE_SUCCESS.equals(result);}//普通方法public static boolean tryGetDistributedLock(String lockKey, String requestId, int expireTime) {Jedis jedis = jedisPool.getResource();try {String result = jedis.set(lockKey, requestId, SET_IF_NOT_EXIST, SET_WITH_EXPIRE_TIME, expireTime);if (LOCK_SUCCESS.equals(result)) {return true;}return false;}catch (Exception e){return false;}finally {jedisPool.returnResource(jedis);}}
}
@FunctionalInterface
public interface Operation {public void execJob();}
抽象基类:把获取锁和释放锁抽象到寄类实现,在具体业务job不用关心这些
@Component
public abstract class AbstractBasicTask {private static final Logger logger = LoggerFactory.getLogger(AbstractBasicTask.class);@AutowiredRedisService redisService;public void doOperation(String taskName,Operation operation){String requestId = DateUtils.getNowTimeMill();// 控制并发锁if (redisService.tryGetDistributedLock(taskName, requestId,600)) {long start = System.currentTimeMillis();try {// 开始执行定时任务operation.execJob();logger.info("{}:执行定时任务完成,耗时(毫秒):{}", taskName, (System.currentTimeMillis() - start));} catch (Exception e) {logger.error(taskName + ":执行定时任务异常", e);} finally {// 释放锁try {redisService.releaseDistributedLock(taskName,requestId);} catch (Exception e) {logger.error(taskName + ":释放锁异常", e);}}} else {logger.info("{}:获取锁失败", taskName);}}/*** 执行JOB业务逻辑*/public abstract void exec();
具体执行任务demoJob
@Component
@EnableScheduling
public class demoJob extends AbstractBasicTask{@Scheduled(cron = "1 * * * * ?")@Overridepublic void exec() {this.doOperation("demoJob", this::testA);}private void testA(){System.out.println("=========");}
}
总结:比较常用的,典型的应用场景,是当我们运算的过程可以抽象成好几个步骤时,把其中相同部分,抽象成公共方法(像上面的common方法),并且把函数式接口作为其入参,在具体业务实现中,使用lambda表达式实现具体业务实现(像上面的method1Operation、method2Operation)。
下一篇:北大青鸟天府校区IT学习大揭秘