edg3/experiment_software_csharp_12_net_8 · Datasets at Hugging Face

title stringlengths 3 46	content stringlengths 0 1.6k
10:218
10:219
10:220
10:221
10:222	SaaS
10:223
10:224
10:225	4
10:226
10:227
10:228	1
10:229
10:230
10:231	4
10:232
10:233
10:234	Depends on application
10:235
10:236
10:237	1
10:238
10:239
10:240
10:241
10:242	FaaS
10:243
10:244
10:245	3
10:246
10:247
10:248	2
10:249
10:250
10:251	3
10:252
10:253
10:254	4
10:255
10:256
10:257	2
10:258
10:259
10:260
10:261
10:262	Why are hybrid applications so useful in many cases?
10:263	In its general meaning, the word hybrid means something whose parts do not share a uniform architectural choice; each part makes a different architectural choice. However, in the case of cloud solutions, the word hybrid refers mainly to solutions that mix cloud subsystems with on-premises subsystems. However, it can also refer to mixing web subsystems with device-specific subsystems, such as mobiles or any other device that runs code.
10:264	Due to the number of services Azure can provide and the number of design architectures that can be implemented, hybrid applications are probably the best answer to the main question addressed in this chapter: how to use the opportunities offered by the cloud in your projects.
10:265	Nowadays, many current projects are moving from an on-premises solution to a cloud architecture, and depending on where you are going to deliver these projects, you will still find many bad preconceptions regarding moving to the cloud. Most of them are related to cost, security, and service availability.
10:266	You need to understand that there is some truth in these preconceptions, but not in the way people think. For sure, you, as a software architect, cannot ignore them. Especially when you develop a critical system, you must decide whether everything can go on the cloud or whether it is better to deliver part of the system on the edge. Therefore, understanding these factors is key to navigating the hybrid landscape, which ensures that you balance cost, security, and availability according to your specific needs.
10:267	It is worth mentioning a real-life example that might clarify the need for hybrid solutions. Recently, several customers of a SaaS solution we offer objected to the fact that they couldn’t move reserved and business-critical documents to the cloud. Our solution was equipping our SaaS with file-handling drivers capable of retrieving files from an in-house document server located in the customer’s private intranet.
10:268	A completely different kind of hybrid solution is the edge computing paradigm. According to this paradigm, parts of the system must be deployed on machines or devices close to the location where they are needed. This helps to reduce response times and bandwidth.
10:269	Mobile solutions can be considered another classic example of hybrid applications since they mix a web-based architecture with a device-based architecture to offer a better user experience. There are lots of scenarios where you can replace a mobile application with a responsive website. However, when it comes to interface quality and performance, maybe a responsive website will not give the end user what they really need.
10:270	Summary
10:271	In this chapter, you learned how to take advantage of the services offered by the cloud in your solutions, as well as the various options you can choose from.
10:272	This chapter covered different ways to deliver the same application in a cloud-based structure. We also noted how rapidly Microsoft is delivering all these options to its customers, as you can experience all of these options in actual applications and choose the one that best fits your needs, since there is no silver bullet that works in all situations. As a software architect, you need to analyze your environment and your team, and then decide on the best cloud architecture to implement in your solution.
10:273	The next chapter is dedicated to building a flexible architecture comprising small, scalable software modules called microservices.
10:274	Questions
10:275
10:276	Why should you use IaaS in your solution?
10:277	Why should you use PaaS in your solution?
10:278	Why should you use SaaS in your solution?
10:279	Why should you use serverless in your solution?
10:280	What is the advantage of using an Azure SQL Server database?
10:281	How can you accelerate AI in your application with Azure?
10:282	How can hybrid architectures help you to design a better solution?
10:283
10:284	Further reading
10:285	You can check out these web links to study the topics covered in this chapter in greater depth:
10:286
10:287	https://visualstudio.microsoft.com/xamarin/
10:288	https://www.packtpub.com/application-development/xamarin-cross-platform-application-development
10:289	https://www.packtpub.com/virtualization-and-cloud/learning-azure-functions
10:290	https://azure.microsoft.com/overview/what-is-iaas/
10:291	https://docs.microsoft.com/en-us/azure/security/azure-security-iaas
10:292	https://azure.microsoft.com/services/app-service/web/
10:293	https://azure.microsoft.com/services/sql-database/
10:294	https://azure.microsoft.com/en-us/services/virtual-machines/data-science-virtual-machines/
10:295	https://docs.microsoft.com/azure/sql-database/sql-database-automatic-tuning
10:296	https://azure.microsoft.com/en-us/services/cognitive-services/
10:297	https://docs.microsoft.com/en-us/azure/architecture/
10:298	https://powerbi.microsoft.com/
10:299	https://office.com
10:300	https://azure.microsoft.com/en-us/overview/what-is-serverless-computing/
10:301	https://azure.microsoft.com/en-us/pricing/details/sql-database/
10:302	https://www.packtpub.com/virtualization-and-cloud/professional-azure-sql-database-administration
10:303
10:304	Learn more on Discord
10:305	To join the Discord community for this book – where you can share feedback, ask questions to the authors, and learn about new releases – follow the QR code below:
10:306	https://packt.link/SoftwareArchitectureCSharp12Dotnet8
10:307
10:308
10:309
11:1	Applying a Microservice Architecture to Your Enterprise Application
11:2	This chapter is dedicated to describing highly scalable architectures based on small modules called microservices. The microservice architecture allows for fine-grained scaling operations where every single module can be scaled as required without affecting the remainder of the system. Moreover, they allow for better Continuous Integration/Continuous Deployment (CI/CD) by permitting every system subpart to evolve and be deployed independently of the others.
11:3	In this chapter, we will cover the following topics:
11:4
11:5	What are microservices?
11:6	When do microservices help?
11:7	How does .NET deal with microservices?
11:8	Which tools are needed to manage microservices?

10:218

10:219

10:220

10:221

10:222

SaaS

10:223

10:224

10:225

4

10:226

10:227

10:228

1

10:229

10:230

10:231

4

10:232

10:233

10:234

Depends on application

10:235

10:236

10:237

1

10:238

10:239

10:240

10:241

10:242

FaaS

10:243

10:244

10:245

3

10:246

10:247

10:248

2

10:249

10:250

10:251

3

10:252

10:253

10:254

4

10:255

10:256

10:257

2

10:258

10:259

10:260

10:261

10:262

Why are hybrid applications so useful in many cases?

10:263

In its general meaning, the word hybrid means something whose parts do not share a uniform architectural choice; each part makes a different architectural choice. However, in the case of cloud solutions, the word hybrid refers mainly to solutions that mix cloud subsystems with on-premises subsystems. However, it can also refer to mixing web subsystems with device-specific subsystems, such as mobiles or any other device that runs code.

10:264

Due to the number of services Azure can provide and the number of design architectures that can be implemented, hybrid applications are probably the best answer to the main question addressed in this chapter: how to use the opportunities offered by the cloud in your projects.

10:265

Nowadays, many current projects are moving from an on-premises solution to a cloud architecture, and depending on where you are going to deliver these projects, you will still find many bad preconceptions regarding moving to the cloud. Most of them are related to cost, security, and service availability.

10:266

You need to understand that there is some truth in these preconceptions, but not in the way people think. For sure, you, as a software architect, cannot ignore them. Especially when you develop a critical system, you must decide whether everything can go on the cloud or whether it is better to deliver part of the system on the edge. Therefore, understanding these factors is key to navigating the hybrid landscape, which ensures that you balance cost, security, and availability according to your specific needs.

10:267

It is worth mentioning a real-life example that might clarify the need for hybrid solutions. Recently, several customers of a SaaS solution we offer objected to the fact that they couldn’t move reserved and business-critical documents to the cloud. Our solution was equipping our SaaS with file-handling drivers capable of retrieving files from an in-house document server located in the customer’s private intranet.

10:268

A completely different kind of hybrid solution is the edge computing paradigm. According to this paradigm, parts of the system must be deployed on machines or devices close to the location where they are needed. This helps to reduce response times and bandwidth.

10:269

Mobile solutions can be considered another classic example of hybrid applications since they mix a web-based architecture with a device-based architecture to offer a better user experience. There are lots of scenarios where you can replace a mobile application with a responsive website. However, when it comes to interface quality and performance, maybe a responsive website will not give the end user what they really need.

10:270

Summary

10:271

In this chapter, you learned how to take advantage of the services offered by the cloud in your solutions, as well as the various options you can choose from.

10:272

This chapter covered different ways to deliver the same application in a cloud-based structure. We also noted how rapidly Microsoft is delivering all these options to its customers, as you can experience all of these options in actual applications and choose the one that best fits your needs, since there is no silver bullet that works in all situations. As a software architect, you need to analyze your environment and your team, and then decide on the best cloud architecture to implement in your solution.

10:273

The next chapter is dedicated to building a flexible architecture comprising small, scalable software modules called microservices.

10:274

Questions

10:275

10:276

Why should you use IaaS in your solution?

10:277

Why should you use PaaS in your solution?

10:278

Why should you use SaaS in your solution?

10:279

Why should you use serverless in your solution?

10:280

What is the advantage of using an Azure SQL Server database?

10:281

How can you accelerate AI in your application with Azure?

10:282

How can hybrid architectures help you to design a better solution?

10:283

10:284