ʂʍɒρƞįł Ҟưȴķɒʁʉɨ (coolsvap), Author at IoT For All

ʂʍɒρƞįł Ҟưȴķɒʁʉɨ (coolsvap)

Swapnil is an Open Source enthusiast with experience in Blockchain, Cloud Native solutions, Containers & Enterprise Software Product architectures. Swapnil is currently associated with research and technology unit in Persistent Systems. He has diverse experience with different private, hybrid cloud architectures with Amazon Web Services, Azure, Google Cloud, OpenStack, CloudStack, IBM Cloud to name a few. He has contributed to different open source projects like OpenStack, Docker, Kubernetes and multiple upcoming open source platforms for containerization. He was previously an Active Technology Contributor(ATC) in OpenStack with contribution history spanned across multiple projects. He also contributed as Core Reviewer in OpenStack Kolla and OpenStack Requirements Project. He is a seasoned technical writer on technology magazines, blogs and also associated as Technical Reviewer with multiple publication houses for technology courses related to emerging technologies and has a passion for learning & implementing different concepts.

How to Use the No-Code Chatbot Builder From Appy Pie

This article provides an introduction to the recently launched visual chatbot builder launched by Appy Pie.

Introduction to Blockchain and Its Implications for IoT Security

Blockchain is as a P2P distributed ledger forged by consensus and combined with a smart contract system. It could reinforce IoT security.

Microservices  Patterns  Part III:  Circuit-Breaking

Circuit-breaking is useful microservices pattern. Conceptually, it's just like an electrical circuit breaker. It's all about failing fast and recovering.

Microservices  Patterns Part II:  Service Discovery

With monolithic applications, services invoke one another through language-level methods or procedure calls. This is relatively straightforward and predictable...

Microservices Patterns Part I :  Event Processing

"Event processing" is a model that allows you to decouple your microservices by using a message queue. Rather than...