Personal details

Dulanjana N. - Remote software architect

Dulanjana N.

Based in: šŸ‡±šŸ‡° Sri Lanka
Timezone: Sri Jayawardenepura (UTC+5.5)

Summary

I have over 10 years of experience in the software engineering field. I have worked with some of the world's leading companies, I'm skilled in Java, Microservices, Kafka, RabbitMQ, solutions architecture, systems design, and more. I'm passionate about mentoring, coaching, and guiding junior developers to help them grow their skills and careers.

Generally, I work from 9 AM to 5 PM but I have flexible work hours.

Read more about me: https://lk.linkedin.com/in/asithan

Work Experience

Senior Technical Lead
WSO2 | Nov 2020 - Present
Java
Azure
TypeScript
React
JavaScript

As a technical lead of the Choreo product, I oversee the development of the cloud-native application development profile. This includes identifying user needs, providing technical guidance to development teams, making architectural decisions, ensuring timely delivery, and managing the roadmap for cloud-native application development tasks.

Previously, I served as the engineering manager for the integration business unit where I oversaw both the team and the delivery of the product, ensuring alignment with the established product roadmap. This initially included overseeing 70 developers. Then I got a few more engineering managers to work under me to provide better engineering management for the overall team.

Education

University of Moratuwa
Bachelor's degree惻Computer Science and Engineering
Jul 2009 - Jan 2014

Personal Projects

API First Integration Thought LeadershipIconOpenNewWindows
2019
RESTful API
Software Architecture
# Key Takeaways - Adoption of APIs by enterprises have increased in leaps and bounds over the past decade. Be it RESTful APIs or not, APIs act as the gateway to your digital enterprise. Therefore it is important to properly manage and maintain APIs to provide a better digital experience for the enterprise stakeholders. - APIs need to be considered similar to business contracts. Design and implementation of APIs (business contracts) can make or break the enterprise's digital business strategy. - Integration-first and API-first are the two widely used strategies in most digital transformation projects; the latter proves to be the most effective and future proof method of the two. - APIs in an enterprise can be categorized as edge, utility, and domain APIs. Edge APIs act as the gateway to the enterprise systems while domain APIs expose the internal systems to the integration layer. Utility APIs contain the integration logic acting as the glue between edge APIs and the internal systems. - In API-first approach, we go through a seven step execution plan. Firstly, we identify the project objectives, then we get to know the enterprise ecosystem. After that, we identify probable integration points of the existing systems, required integration capabilities and use cases. Then for each identified use case, we design the APIs beginning from edge APIs and finally implement the integration. InfoQ Article: https://www.infoq.com/articles/api-first-integration/ Video link to a speech I gave based on this. https://www.youtube.com/watch?v=Ie9Z8nnK_io

Certifications & Awards

Leadership Essentials
Cornell University | Nov 2021
Advanced Diploma in Management Accounting
CIMA | Jul 2012