현수근 Email & Phone Number

대한민국 서울

폐기물 온라인 솔루션 Upbox 기능 및 성능 개선1. 기술부채 해결을 위한 설계A. email 1. 기존 문제점 - 기존 javamail라이브러리 내부에서 전송 단위별 connection을 별도 생성하여 메일을 전송하고 connection을 close하는 로직 2. 해결방안 - 기존 메일 전송 로직에서 batch형태로 전송시 connection생성하는 부분을 재사용하는 형태로 변경B. batch처리 1. 기존 문제점 - Identity방식으로 채번을 생성하는 테이블에 insert시 Spring Data JPA의 batch형태의 메소드를 사용함으로 인한 insert, update수행 속도 하락 - update수행속도 저하에 따른 다른 기능에서 데이터 접근시 간헐적으로 lock발생 2. 해결 A. 기존 Spring Data JPA방식이 아닌 JdbcTemplate의 batch메소드를 이용하여 수행속도 향상 - Insert의 경우 rewriteBatchStatements옵션 추가 - Update는 임시테이블에 변경하고자 하는 데이터를 insert후 변경하고자 하는 테이블과 임시테이블을 join하여 수행 B. 기존 모든 레코드에 대해서 하나의 트랜잭션으로 처리했던 부분에 대해서 lock발생 가능성을 최소화하기 위해 특정 범위 단위로 트랜잭션 범위를 축소화 C. B에서 지정한 트랜잭션 범위 단위별 별도의 CompletableFuture을 할당하여 기존 순차적인 blocking방식에서 non-blocking방식으로 처리하도록 변경함으로서 요청처리량 및 응답속도 향상 D. Insert시 식별자는 ResultSetMetadata를 통해 batch로 수행된 레코드들의 식별자 목록을 가져오도록 JdbcTemplate 확장

대한민국 서울

기존 MVP제품의 출시를 위한 기술부채 해결1. 기술부채 해결을 위한 설계A. 기존 문제점 : Sendbird시스템 임계치로 인한 429에러, 사용자당 채팅채널 2000개이상 생성불가 등의 기술부채로 인한 서비스 품질 향상에 제약 존재B. 화면은 기존 외부 채팅창에서 자체 게시판 기반 webview기반으로 변경C. 채팅방, 채팅 내역 등은 실시간으로 변경이 잦아 IO가 발생빈도가 높아 redis에 저장2. 기존 Sendbird를 통한 push를 Braze push로 전환A. push메시지를 특정 사용자에게만 보내는 귓속말 기능이 불가하고, 자체 마케팅 형태의 대량 push기능 불가한 제약 존재B. push가 현재 필요한 기능 및 향후 필요한 기능 수집한 결과 Braze에서 제공하는 기능이 대부분 일치하여 Braze로 대체3. Postgresql DB replication를 통한 Primary(Write), Secondary(Read)분리A. 기존 문제점i. 서비스가 기능별 목록 조회 후 세부 항목에서 추가/수정하는 형태로서 조회가 빈번하며 데이터 레코드수가 많아서 부하를 발생시킬 가능성이 존재ii. 하나의 레코드에 대해서 사용자의 액션에 따라 상태가 전이되어 update해야 하는 경우가 빈번하여 lock 가능성 존재B. DB replication환경에 따른 어플리케이션에서 조회와 추가/수정 기능 분리i. Transactional readOnly, REQUIRES_NEW, select -> master인 경우도 존재

대한민국 서울

1. major role : Senior Software Development2. application2.1 Development of API function according to synchronization request for IRP (personal retirement pension), electronic finance, and installment business rights2.1.1 Development of a common module for IRP data inquiry required by banks, financial investments, and insurance2.2 Back-end design for synchronization requests from clients and users2.2.1 Publish the client request to the kafka queue, quickly respond, consume the client request published by the module for each industry, receive the result of calling the API of the information provider, store it in the data storage, and publish the result of the call to another kafka queue. - Communication with information provider (external): REST (according to standard API spec) - Internal system communication: GRPC2.2.2 As a method to minimize response time to users by receiving client requests, async processing by placing a queue for requests and a response queue for processing results in the middle instead of in the form of request~response.

대한민국 서울 강남구

1. major role : Senior Software Development and Application Architect2. application 2.1 3rd integration framework 2.1.1 OAuth2(Authorization Code, Implicit, Resource Owner Password Credentials) 2.1.2 OIDC(JWT, JWS, JWK) 2.1.3 SAML(HTTP Post Binding, HTTP Redirect Binding) - AWS Management Console, New Relic 2.1.4 LDAP MS Active Directory - Doosan Corp. 2.1.5 MS ADFS(OIDC, JWT, JWS, JWK) - Samsung CorpAD 2.2. The authentication and authorization and single sign on based on the OAuth2 technology 2.2.1. Converting the previous SAML2 authentication into the new OAuth2 authentication 2.2.2. The single sign on implementation to support OAuth2 multi-domain 2.2.3. OAuth2-based White-Labelling (business type in which intermediary service providers provide intermediary services under their brand name 2.3. SAML2 concurrent support for AWS Management Console interworking 2.4. The Saas service based on the AWS marketplace 2.5. OAuth2 Authorization Server Session-Clustering 2.5.1. o session clustering support using Hazelcast IMDG to solve sessions problems when replicated OAuth2 authentication server 2.5.2. embedded Hazelcast 2.5.3. Provides the ability to automatically find and connect session clustered EC2 devices using the AWS Hazelcast Discovery plugin to add and deploy EC2 instances even in service

대한민국 서울 종로구

1. major role : R&D based on the open source, In-house framework2. application 2.1. Building a company-specific framework 2.1.1. The UI-Adapter framework for interworking with RIA platform - Process request and response data in the form of Map, VO-based POJO in the same standardized interface that is not dependent on various RIA platforms 2.1.2. A framework for querying and manipulating data with the same standardized interface for various methods for DB connection – iBatis, MyBatis, Groovy 2.2. The replacement of prebuilt frameworks 2.2.1. Changed and replaced projects based on LG Devon and Samsung Anyframe based on Spring Framework due to maintenance cost and license avoiding 2.2.2. Converting prebuilt custom framework based on egovframework 2.0 into the new one based on egovframework 3.x 2.2.3. The SAP, XML Web Service Adapter based on the spring framework - SAP Java Connector, Apache CXF integration 2.2.4. The framework segregation in which the framework source is ported to the project into a separate project, and provide the build output to the project in the form of a library to unify the development environment 2.3. Standard interface-based module for commercial SW integration 2.3.1. G-PIN, SMS, Mail, DB encryption/decryption … 2.3.2. Batch(jobPass), Report(m2soft), DRM(markany), SSO(softforum), search-engine(wisenut), Interval Encryption(xecureweb)

대한민국 서울 종로구

1. major role : Senior Software Development2. application 2.1. Developed an administrator site to register and manage devices and friends in CPNS 2.1.1. design / development of XML interface to receive request from PC Suite (App.) To manage device information by CPN 2.1.2. buddy request to other buddy, request/cancel buddy list and request accept / reject

대한민국 서울 강남구

1. major role : Junior Service Development2. application 2.1. SKT MMS Gateway Architecture Transformation[Struts -> Spring framework] 2.1.1. Changed the existing Struts 1.2.x base to Spring 2.5 framework, based on JDK 1.5 2.1.2. The removal weblogic-dependent code through converting weblogic-MQ base into JMS queuing one, and refactor application in the form of reliable message transfer 2.1.3. MMS gateway implementation - The receipt SOAP messages (MM7, MM4) - The inquiring subscriber information about MMS receiver - The message sent to SKT MMS network and receives result - The billing file generation according to SKT MM8 format

대한민국 서울 금천구

1. major role : Junior Development2. application 2.1. The web/wap site to provide network operator's(SKT, LGT, KT) ringtone and voice service (ARS) 2.1.1. the ringback tone download / gift and preview through the ringback tone download server 2.2. SBSi Mobile portal 2.2.1. Mobile contents download / gift linked to 3 mobile operators 2.2.2. Weekly SMS messages for entertainer's schedule and SBS program 2.2.3. The development of integration module for contents downloading/gifts and billing requests/approval - The available wap site for downloading/gifting contents - The TCP connection for billing 2.3. The feeling service called the ringback tone of the LG Telecom 2.3.1. Monitoring system(O&M) - Periodically polling resource information of Agent (managed device) and alarm occurs when threshold is exceeded - Receive Agent Trap message from JMS Queue and forward it to client - Client (GUI) Receive the request to TCP and forward it to SNMP agent (UDP) to deliver the result. 2.3.2. The VM(Mobile Application) : J2ME 2.3.3. The portal(Web) : The web site to provide the feelring contents