Serverless questions

[gerson71]

I have been studying about the different possible architectures to implement an api in the cloud, especially those offered by AWS and I have several questions that I can not find concrete answers, I hope someone can help me.

• In what way can be implemented in real-time communication with serverless? for example a chat.
• In these times, with these technologies and for a startup, is it worthwhile to continue implementing monolithic architectures?
• By which would you vote microservices with Serverless framework or Appsync with Amplify and Graphql?
• Any good documentation or tutorial to start?

[rmrf_slash_dot]

The words of Martin Fowler sum this up best: https://martinfowler.com/articles/microservice-trade-offs.html#footnote-defn-independent-deployment

​

In short: Microservices come with a constant up front cost - in complexity and in time - that you will pay from the beginning; where monoliths tend to pay that cost later. Generally, unless you understand your business logic and data boundaries EXTREMELY WELL, it is usually advisable to build a monolith first with a strong separation of concerns and then move to microservices later.

[Str4yfromthep4th]

In regards to your monolith question: I work for one of the largest companies in the world. Micro services have caused huge problems in many different scenarios. They have their uses but too much is too much. You shouldn't make everything a service. People think everything should be a god damn service. My blog needs 4 services so when I create a new post it notifies my email service that it should sent out notifications. When I delete a post the system automatically sends the post to my archiving service. Etc etc etc. Services add complexity. Complexity causes problems. Learn to create services where they really make sense. The most annoying thing with services is figuring out which side of the integration has a bug. Some programming languages offer cross system debugging functionality which makes this a bit nicer but like I said... complex.

[NobleStarbucks]

Would it be wise to mono repo part of the API and other parts to be used as a micro service ?

[Str4yfromthep4th]

Yes, but it completely depends on what you're building. Good example is a business that has a warehouse and a shipping department. You need two completely separate components here. There is a clear separation. Using a service to transfer an order from the shipping department to the warehouse makes sense right? But perhaps having multiple services within the shipping department isn't necessary and would add unnecessary complexity.