December 2017
Intermediate to advanced
468 pages
13h 12m
English
Services should be stateless as much as they can. Statelessness is another important principle that helps services to lower the consumption of resources, test in isolation, and reusability. To implement statelessness in the email service, it needs all the necessary information explicitly for sending emails, and so it does not need to pick up additional information from a database or any other resources as its focus is on the business logic of setting up schedules to send emails. The schema can have more details (message, email IDs, subject) explicitly, rather that just booking ID, and make an email service to pick up additional information from the database for that booking ID.
Read now
Unlock full access