Welcome back to Sansan Global Development Center blog! I'm Vani from the Engineering Team, and I'm excited to share our team's journey and development process with you. In this blog post, we'll dive into the evolution of our engineering team in Cebu, our adoption of Agile Scrum methodology, and our exploration of the Bill One architecture and its technology stack. From team building to embracing Agile principles and navigating complex architectures, join us as we uncover the key milestones and insights that have shaped our journey. Let's dive in!
Building Our Engineering Team
Our journey at the Cebu Development Team began with a small but dedicated team of three individuals. Under the guidance of our Product Lead (PdL) and Technical Lead (TL) from the Japan Team, we embarked on our first backlog with determination and enthusiasm. Their support was invaluable, as the PdL clarified project specifications and the TL ensured code quality standards were upheld.
As our workload expanded, so did our team. With each new member, we gained fresh perspectives and expertise, allowing us to tackle increasingly complex projects with confidence. Today, our team is sizable and well-established, yet our commitment to continuous improvement remains unwavering.
Our journey has taught us the importance of collaboration and adaptability in achieving our goals. By fostering a culture of innovation and mutual support, we've laid a solid foundation for Sansan's future breakthroughs.
Embracing Scrum Principles
Embracing agility, we wholeheartedly adopted the Agile Scrum methodology, though initially navigating our first backlog unconventionally. Aligned with the Scrum Guide and in sync with our peers in Japan, we adjusted our approach to ensure adherence to best practices. Following the rhythm of Scrum events, including bi-weekly sprints, we embarked on a determined journey towards our goals. These are the pivotal events that shaped our pragmatic approach.
Scrum Events
Daily Scrum: Every day, we meet up for a quick chat to sync our efforts and spot any problems.
Sprint Planning: We plan out our next chunk of work, using past experiences to guide us.
Sprint Review: We show off what we've done to our stakeholders, get feedback, and celebrate our wins.
Sprint Retrospective: After each round of sprint, we take a moment to look back, figure out what went well, and how we can do better next time.
Unraveling the Bill One Architecture
As we embarked on our journey to understand the Bill One architecture and its intricate technology stack, we found ourselves immersed in a world of challenges and opportunities that would ultimately shape our personal and professional growth. At the forefront of our exploration were the cutting-edge technologies powering Bill One:
And to visualize the architecture of Bill One. Below is an architecture diagram showcasing Bill One ecosystem:
Constructed atop the reliable infrastructure of Google Cloud Platform (GCP), our web application, Bill One, embodies a meticulously organized workflow. When users send requests, they are seamlessly directed to the load balancer, which efficiently routes them to the Backend For Frontends deployed on App Engine. These requests then traverse through our backend microservices hosted on Cloud Run. Our data integrity is upheld by secure storage mechanisms provided by Cloud SQL and Cloud Storage services, ensuring both robustness and scalability.
By adopting a microservices architecture, we prioritize modularity and autonomy, allowing each service to focus on a specific business function. This approach enhances agility, as updates and changes can be made independently without affecting the entire system. Additionally, microservices enable easier scalability, as resources can be allocated more efficiently based on demand. Overall, the use of microservices over a monolithic approach ensures that the Bill One platform remains adaptable and responsive to evolving business needs.
Future Perspective
As we reflect on our journey so far, the future brims with possibilities. With each challenge we overcome and every lesson we learn, we grow stronger and more resilient. Our commitment to innovation and excellence remains unwavering as we continue to push the boundaries of what's possible in software development.
Next Blog
We hope you've enjoyed this glimpse into our development process and the intricacies of the Bill One architecture. In our next blog post, we'll delve deeper into our team structure, sharing insights into how we organize and collaborate to drive success. Join us as we explore more development experiences and unveil the secrets behind our continued growth and success. Stay tuned for more exciting updates from the Sansan Global Development Center!
