Docker is an open platform for developing, shipping, and running applications. Docker enables you to separate your applications from your infrastructure so you can deliver software quickly. With Docker, you can manage your infrastructure in the same ways you manage your applications.
Abstract Class Vs. Interface use case scenarios:
USE AN ABSTRACT CLASS
1). When creating a class library which will be widely distributed or reused — especially to clients, use an abstract class in preference to an interface; because, it simplifies versioning. This is the practice used by the Microsoft team which developed the Base Class Library…
Distributed Transaction is one that spans multiple databases across the network while preserving ACID properties. If a transaction requires service A and B both write to their own database, and rollback if either A or B fails, then it is a distributed transaction.
Microservices guidelines strongly recommend you to use the Single Repository Principle(SRP), which means each microservice maintains its own database and no other service should access the other service’s database directly. There is no direct and simple way of maintaining ACID principles across multiple databases. This is the way the real challenge lies for transaction management in Microservices.
The Risk of the Microservices Architecture :
The microservices architecture moves application logic to services and uses a network layer to communicate between them. Communicating over a network instead of in-memory calls brings extra latency and complexity to the system which requires cooperation between multiple physical and logical components. The increased complexity of the distributed system leads to a higher chance of particular network failures.
With a microservices architecture, we need to keep in mind that provider services can be temporarily unavailable by broken releases, configurations, and other changes as they are controlled by someone else and components move independently…
Important points for Securing our .Net Core Application.
1. Make your Login more secure
2. Always submit sensitive data using Encryption
3. Don’t forget to clear Cookies when logout
4. Always use SSL
5. Never keep sensitive data in clear form in your Database
6. Audit Trails or Logging is also Important
7. Never display original Technical error to the End-User
8. Cross-Site Scripting (XSS)
9. Try to Hide your .Net Core Version
10. Cross-Site Request Forgery (CSRF)
11. LINQ can protect from SQL Injection
12. Streams Deserialization can be tempered
13. Always keep your Framework & Libraries Updated
Recently in a project I got a chance to explore Azure Event Hubs and I really liked it, it’s a brilliant service from Azure for some targeted scenarios. I thought to share it here in a simple way.
when you want to emphasize that what you are about to say is obvious and to be expected in the circumstances.
Needless to say, we’re right at the back.
Needless to say, it was not there for long.
Our rat got out of its cage. Needless to say, the cat caught it.
Cloud Computing is a new buzz in the market and getting popularity day by day . Microsoft Azure is one of my favourite Cloud so after wrapping up my head around Microservice Architecture , It’s time to create and deploy back-end microservices to Azure Container Service (AKS). This is my 6th article and here i’ll be describing step by step how to deploy & run microservices to Azure Kubernetes.
Application Architecture & Deployment
The Azure Container Service (ACS) is a cloud-based container deployment and management service that supports popular open-source tools and technologies for container and container orchestration.