FROM ENTITY RELATED
TO USE CASE-SPECIFIC SERVICES
SINGLE RESPONSIBILITY PRINCIPLE APPLIED TO EXTREME
OCTOBER, 25, 6:00 PM (EEST)
Senior .NET developer
Then we can refactor our system in a way to be suitable to exist in such an ecosystem (microservice/serverless)
In the era where everyone pushes toward microservices and serverless, it’s a good idea to know and understand the concept of Single Responsibility from an ideological standpoint.
We will talk about:
What is an Entity-oriented service, where it fits and what are its cons
How do we refactor such a system to make it more flexible
What is segregation, and why it matters
Senior .NET developer at Ciklum
5+ years of experience and knowledge in a wide range of technologies.
Well-versed in cloud technologies and Microsoft Certified Azure Developer.
Passionate about new technologies with an emphasis on Functional programming and Cloud.
Join us if you’re passionate about tech, and eager to expand your expertise in refactoring and segregating big services.
We’ll use C# in all examples and demos. However, the ideas apply to all languages!
Since 2002, we’ve engineered technology that redefines industries and shapes the way we live
clients reached IPO stage
seasoned like-minded experts globally
client domains: healthcare, fintech, travel, sportswear, entertainment, security