How to implement a universal Redis addition, deletion, modification and query script

1. Think about what duplicate codes there are?

 If it is just for simple addition, deletion, modification, and query, then you only need to tell me which class needs to be serialized and deserialized, and tell me what the prefix of the key is, right? As for the expiration time, we can ignore it this time. If we need to add the expiration time, it is not a difficult thing. Then we think about it for a while and use generics in Java to get the following basic class:

2. Basic service class

public class BasicDataRedisService<t> {

    /**
     * Redis key prefix String
     * Redis中的key前缀
     */
    private String prefixString;

    private Class<t> targetClass;

    @Autowired
    private StringRedisTemplate redisTemplate;

    public BasicDataRedisService(String prefixString, Class targetClass) {
        this.prefixString = prefixString;
        this.targetClass = targetClass;
    }

    // -------------------------以下为内部使用---------------------------------

    protected String generateKey(String id) {
        return prefixString + "id:" + id;
    }

    protected T getByKey(String key) {
        T result = ValueRedisUtil.getRedisObject(redisTemplate, key, targetClass);
        return result;
    }

    protected boolean setByKey(String key, Object object) {
        return ValueRedisUtil.setRedisObject(redisTemplate, key, object);
    }

    protected boolean deleteByKey(String key) {
        return ValueRedisUtil.delRedis(redisTemplate, key);
    }

    // -------------------------以下对外提供---------------------------------


    /**
     * 根据id获取
     *
     * @param id
     * @return
     */
    public T getById(String id) {
        String key = generateKey(id);
        return getByKey(key);
    }

    /**
     * 根据id刷新
     *
     * @param data
     * @param id
     * @return
     */
    public boolean setByModel(Object data, String id) {
        String key = generateKey(id);
        return setByKey(key, data);
    }

    /**
     * 根据id删除
     *
     * @param id
     * @return
     */
    public boolean deleteById(String id) {
        String key = generateKey(id);
        return deleteByKey(key);
    }

}</t></t>

3. Customize a query service class

Suppose we want to query users, then we only need to write like this:

@Service
public class UserRedisServiceImpl extends BasicDataRedisService<user> {

    private static String PREFIX = "henbao:user:";

    public UserRedisServiceImpl() {
        super(PREFIX, User.class);
    }
}</user>

4. Think about the disadvantages of writing like this

Although writing this way saves the amount of code and can achieve the convenience you want, I always feel that something is wrong, and the operation seems to be a little more exciting. Boy, if you can have such an idea, then congratulations, you have a higher pursuit of code. We have written the class twice now, and written constants to show what the prefix in Redis is. When we use Spring, we usually don't tell the underlying framework these things. We usually use annotations, right? Therefore, Redis Repositories comes on stage.

5. Each has advantages and disadvantages

 Although we are very happy to write this, some developers hope that the content stored in redis is completely consistent with the Model in the db layer, and after modifying the database table structure, it still remains the same. There will be a wave of reverse generation coverage... Then please develop it yourself and submit more powerful code for Spring! At present, it is recommended to use this method if you have a separate redis layer model. Of course, it has all the problems that should be encountered in annotation scanning. Just be patient when dealing with it.

The above is the detailed content of How to implement a universal Redis addition, deletion, modification and query script. For more information, please follow other related articles on the PHP Chinese website!