70-533: Implementing Microsoft Azure Infrastructure Solutions – Bestdotnettraining
Tired of doing the same routine and mundane job…
Break the barrier open yourself to the world of completely new opportunities. Expand your Horizon and Vision about Cloud Computing. Be an actor and not a spectator in how cloud computing is encompassing the IT industry.
Whether it is a Startup, Midscale or Large Organization, all are now moving away from On-Premise infrastructure to Cloud Infrastructure. Virtual Network and Virtual Machines are taking over providing the advantage of Pay-As-Go model and ability to scale infrastructure if need be. Whether it is a Simple Website or E-commerce Portal or CRM or Office Automation tools or DevOps tools or anything which needs Server Infrastructure – all are now finding their space in Cloud.
Today knowledge of cloud computing is as essential as knowledge of OS for effectively using the system.
In Microsoft Build conference, Microsoft shared with the world how large its cloud platform is and who is using these services. They boosted that they have more data centres than Amazon Web Services (AWS) and Google’s Cloud Service combined and that 85% of Fortune 500 companies are currently using Azure in some or the other capacity. TIME TO LEAVE YOUR COMFORT ZONE AND keep in tune with the developments for your personal career growth– ACCEPT the fact that CLOUD IS THE FUTURE
What is Azure 70-533?Knowledge about the components of the Azure architecture, including the tools, infrastructure and portals are the key focus areas in the training course of AZURE 70-533 which is primarily Infrastructure solutions. The primary highlights, of this course, are, creating Azure virtual machines, configuring and deploying storage solutions and data services
Who needs the AZURE training?This, Microsoft Azure training is targeted for ANYONE who wants to move their current skillset to Microsoft Azure cloud, taking the benefit of unlimited computing, storing and networking power, for personal career growth.
How the training is delivered?The Microsoft Azure course will enable you to design, build, maintain and monitor robust and scalable cloud solutions and most important you will start thinking BIG. This course also focuses on the architectural considerations and decisions necessary when building a highly available solution in the cloud.
Teaching methodology of Mr Sandeep Soni an industry expert is pretty simple, every topic begins with concepts, to position the candidate in a comfortable state to understand what is being talked about, followed by practical demos of, how the feature can be incorporated in real-time situations.
You can experience this by looking at some of his demo videos of Microsoft Azure as listed below and you can also visit.
This article explains the Libraries in .NET, Types of DLL, and Assemblies in .NET and its structure, Namespaces and Internal Access Specifier.
I. Introduction to Libraries
Dynamic Linking Library: A DLL is an application which can have everything that an EXE can have. The difference between them is, an EXE can execute independently but DLL cannot. The code in the DLL can be reused in many other applications but the code in EXE cannot be reused.
II. Types of DLL in Windows OS:
1. Win32 DLL: Here the code is available in the form of simple “C” functions.
2. COM DLL: This DLL has code in the form of reusable COM Components. These are also referred to as ActiveX DLL
3. .NET DLL: These DLL’s (Portable Executables) are used for distributing the reusable classes to various types of .NET applications.
• The Portable Executable (PE) format is a file format for executables, object code, DLLs, FON Font files and others used in 32-bit and 64-bit versions of Windows operating systems
• PE is a modified version of the Unix COFF file format. PE/COFF is an alternative term in Windows development.
• Microsoft’s .NET Framework has extended the PE format with features which support the Common Language Runtime (CLR).
• The CLR section of it contains two important segments: Metadata and Intermediate Language (IL) code
III. What is Assembly in .NET
An assembly is a collection of types (classes, interface, struct etc…) and resources (bmp, jpg, string table, txt, ico) that are built to work together and form a logical unit of functionality. An assembly provides the common language runtime with the information it needs to be aware of type implementations. To the runtime, a type does not exist outside the context of an assembly.
Assemblies are a fundamental part of programming with the .NET Framework.
• It contains code that the common language runtime executes.
• It forms a security boundary.
• It forms a type of boundary.
• It forms a reference scope boundary.
• It forms a version boundary.
• It forms a deployment unit.
• It is the unit at which side-by-side execution is supported.
Note: We should create a multifile assembly when you want to combine modules written in different languages and to optimize downloading an application by putting seldom-used types in a module that is downloaded only when needed
Note The files that make up a multifile assembly are not physically linked by the file system. Rather, they are linked through the assembly manifest and the common language runtime manages them as a unit.
Assembly Manifest Content:
1. Assembly Name
2. Version Number
4. Strong name information
5. List of all files in an assembly
6. Type reference information of types exported from the assembly
7. Information about other referenced assemblies
IV. About Namespaces
• A namespace is a logical collection of classes and other types with unique names. In a given namespace all the types have a unique name and thus it is used to resolve the ambiguity in case of a name conflict.
• Any type when used outside the namespace, it must be qualified by its namespace, but when used by another type within the same namespace it need not be qualified by the namespace.
• We can use using Namespace on top of the file so that we don’t have to qualify all the types of that namespace in that file explicitly.
V. Internal Access Specifier
• A public Class is accessible within and outside the assembly. Whereas an internal class can be accessed only by other types within the same assembly (irrespective of the namespace of other classes within the assembly).
• Internal is the default access specifier for the class.
• The top-level class can only be declared as either public or internal but nested class (a class within class) can have any access modifier.
• The namespace can never be used as a boundary for an access specifier. It’s used only as a name qualifier.
• An internal member of a class is accessible to all other types within the same assembly and is not accessible outside the assembly.
• A member declared as “protected internal” is accessible to all the class within the assembly and only to the derived classes outside the assembly.
• A public method of a public class cannot have either as a parameter or return type any data type of the same assembly which is not public (or is internal).
VI. Types of Assemblies:
1. Private Assemblies: An assembly whose local copy is maintained by each & every application referencing to it.
2. Shared Assembly: An assembly whose single copy deployed in Global Assembly Cache (GAC) and used/shared by many applications running on that machine. Such assemblies must have a Strong name.
3. Satellite Assembly: A resource-only assembly for a given culture is called as a satellite assembly. They don’t have any code but they have only resources like string tables and images.
4. Dynamic Assemblies: These run directly from memory and are not saved to disk before execution. You can save dynamic assemblies to disk after they have executed. The API method Reflection. Emit is used to create dynamic assemblies
This article explains all about Cloud Computing. Topics covered:
• What is Cloud Computing?
• Why businesses are moving to Cloud?
• Cloud Characteristics.
• Cloud Computing Service Models – IaaS, PaaS, SaaS.
• Deployment Models in Cloud Computing.
• Advantages and Disadvantages of Cloud Computing.
• Cloud Computing Job Roles.
• Cloud Computing Platforms and Certifications.
I. What is Cloud Computing?
Cloud: a metaphor for the Internet.
Cloud Computing: A type of Internet-based computing where different services — Storing and accessing data and programs over — are delivered to an organization’s computers and devices through the Internet.
A cloud computing service consists of highly optimized data centres (third-party data centres from the end user point of view), that provide various hardware, software and information resources (when needed).
Why is Cloud Platform preferred?
• The cloud platform is preferred because it hides the complexity of the underlying infrastructure from users and applications by providing a very simple graphical interface or API (Applications Programming Interface).
• The Cloud platform provides on-demand services that are always on, anywhere, anytime and anyplace.
II. Why are businesses moving to cloud?
In traditional hosting, a software company has to deal with-
• Licensing costs
• Protection of data
• Frequent upgrades to latest technologies/versions
• Maintenance and up -gradation of hardware and most important, find the right skill sets at the right time. Businesses today, are moving to Cloud because of its amazing characteristics as below.
III. Cloud Characteristics
Characteristics of Cloud computing-
Remotely hosted: Data or services are hosted on a remote infrastructure.
Ubiquitous Data or services are available from any place through the internet.
Resiliency: To minimize downtime in the event of a disaster, Cloud providers generally mirrors solutions to multiple data centres.
Self – service and On-demand: A consumer can himself provide computing capabilities, such as server time and network storage, automatically as required without requiring human interaction with each service’s provider. It is sold on demand mostly by the minutes or hours. (Pay as you go model)
Elasticity – A user can utilize the cloud service as much/ less as required.
Broad network access– Capabilities are available over the network and can be accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
Fully managed by the provider – The user is unaware of the details of how the service is managed in the cloud. For example, the user need not worry about aspects such as hardware that is used, software updates and patches, plug-ins, web security. There is an optimum utilization of resources and as well as the sharing of these resources. All is taken care of by the provider.
a. Delivers computer infrastructure (a platform virtualization environment) as a service.
b. Cloud providers build data centres, scale, hardware, networking, managing power, storage, distributed systems, etc…
c. Rather than purchasing servers, software, network equipment, data centre space or clients, buy those resources as a fully outsourced service. Example: Amazon Web Services(AWS), Rackspace Hosting, VMWare, Citrix, Azure, Google Cloud
2) PaaS (Platform as a Service):
a. Provides necessary tools to the developers to create, test, host and maintain created applications.
b. Cloud providers offer an Internet-based platform to developers who just create services but don’t prefer to build their own cloud.
Example: Microsoft Azure, Google Cloud, AWS
3) SaaS (Software as a Service):
a. SaaS is a software delivery methodology which provides licensed multi-tenant access to software and its functions remotely as a Web-based service.
b. From end user’s point of view, applications are located in the cloud and it is almost always accessible through a web browser.
c. Any application which is hosted on a remote server and can be accessed over the Internet is considered as SaaS.
Example: Microsoft Azure, Gmail, Google Apps (Office-like features), Sales Force CRM
V. Deployment Models in Cloud Computing
1. Private Cloud:
o A private cloud hosting solution is also known as an internal or enterprise cloud, resides on a company’s intranet or hosted data centre where all of your data is protected behind a firewall.
o This can be a good option for companies who already have expensive data centres because they can use their current infrastructure.
o You opt for a private cloud when you have strict security and data privacy issues.
o Cons: The main drawback people see with a private cloud is that complete work of management, maintenance and updating of data centres is the responsibility of the company.
2. Public Cloud:
Public Clouds are the ones which are open for use by the general public and they exist beyond the firewall of an organization, fully hosted and managed by vendors. Your data will be stored in the provider’s data centre and the provider is responsible for the management and maintenance of the data centre. Because you share computing resources among a network of users, the public cloud offers greater flexibility and cost savings. This is a good option if your demand for resources fluctuates. You will just purchase the capacity on the basis of usage and can scale up or scale down server capabilities based on traffic and other dynamic requirements. The public cloud environment is appealing to many companies as it reduces lead times in testing and deploying new products. Cons: They are more vulnerable than private clouds and there is no control of who uses/ shares the resources. Note: Even though you don’t control the security of a public cloud, all of your data remains separate from others and security breaches of public clouds are extremely rare.
3. Hybrid Clouds:
Hybrid Clouds are a mix of public and private clouds, consisting of external and internal providers. Secure apps are managed by the organization and the not-so-secure apps by the third party vendor. For example, you can use a public cloud to interact with the clients but keep their data secured within a private cloud. Most companies are now switching to Hybrid clouds. Hybrid Clouds are Ideal in situations where you have planned are to migrate to a complete cloud solution as existing hardware expires or you have some applications or hardware that are not ready for the cloud.
VI. Advantages and Disadvantages of Cloud Computing
By taking a closer look on a Dependency Injection (DI) , we can understand it is a software design pattern which allows us to develop a loosely coupled code and it also decreases the code dependency of components of the tightly coupled software. It is also known as Inversion-of-Control, which helps us to do the unit testing more convenient.