Microservices are the current big thing in software architecture. Find out about their use cases and why they are so popular.
- [Instructor] In our application,…we will use microservices.…They are the big topic…in software, architecture, and development.…Let's explore what they actually are in depth.…First, let's look a bit…into history of software architecture.…Until 20 to 30 years ago,…architectures were strictly monolithic,…which means they consisted of one single application.…If you wanted to modify code,…you had to check out the whole application…from your version control system,…and then your change was ready to go into production,…it was deployed with the whole application.…
Usually, these applications were also…ran on a single server.…The program logic tended to be very tightly coupled.…This means, if you changed the method…of functioning one file,…there was a significant chance that your action…would affect other parts of the application.…This means that the developer had to have a model…of the whole application in mind when doing any change.…When a new developer started to work on something,…she or he needed to first understand…
After explaining some basics about Node.js and microservices, Daniel shows you how to sketch out the planned architecture for your application and get the boilerplate code, modules, and credentials in place. Next, he shows how to create a bot user in Slack, connect to Slack, and post messages. He also shows you how to get your bot to process variations in text by creating logic that delegates the processing of intent to dedicated modules. Lastly, he shows how to register additional services and he covers how to use monitoring to identify architectural or performance issues.
- Using Slack APIs
- Sketching out a Slack bot architecture
- Setting up a project and choosing modules
- Creating and naming your bot
- Connecting to Slack
- Setting up and using natural language processing
- Routing by intents
- Implementing geocoding and time calculation
- Adding and monitoring services