Volkan Guneri’s Post

Is it possible to deploy a web application for free? Is the "free lunch" only in a mousetrap? To answer briefly - yes, you can deploy an application for free. But it's not suitable for all projects. Many probably remember `git push heroku master`. Since then, a lot of time has passed, and such a free solution from Heroku no longer exists. But this doesn't mean that competitors are standing still and there's nothing similar in the market. There's, for example, render.com, which essentially offers the same - a limited instance with the ability to deploy your project from source code very easily. Of course, there are a bunch of downsides. Firstly, the limitation of resources. Something big obviously won't even launch. The last thing I depoyed there was a small project in the blockchain sphere with practically no backend. The main thing the application does is serve static content (React + Next). Secondly, one of the most significant downsides, in my opinion, is that the application goes to sleep if there are no requests to it, and the "wake-up" time can be very unpleasant. The platform's personal account has this warning: "Your free instance will spin down with inactivity, which can delay requests by 50 seconds or more." It's can be forever. Although, if you look at the documentation, there is a recommendation to set timeouts for 120 seconds. Waiting 2 minutes for the application to open is very bad. But is there a way around this? Why not. The application only sleeps if there have been no requests for a certain period of time (about an hour). Why not set something like a cron job that will make a request to the application every few minutes. Fortunately, there are services on the internet that will do this for free. This is one example that might help someone launch their micro-project without investment. P.S. Somebody will say you can also run a server at home based on your old computer. There's some truth in this, however, a static IP still costs something. P.S.S. Hmm. What about scalability? What if for each new instance, create a new account and a Load Balancer in front of them? Okay, okay, I'm just speculating. Or am I? 😅

Discover amazing free resources for developers at https://free-for.dev. This curated list includes tools and services like cloud platforms, APIs, monitoring, and more - all available at no cost. Whether you're a beginner or an experienced developer, you'll find something useful to enhance your projects without breaking the bank. Take a look and start leveraging these free resources today!

Thanks @Andy Conley for this very good article showing how to achieve App Availability and Resiliency in a eaysy way. The power of WASM is there to grasp with NGINX Unit. Please read through and see the potential.

#snsinstitutions #snsdesignthinkers #designthinking API keys are unique identifiers assigned to users or applications to authenticate and authorize their access to an Application Programming Interface (API). These keys play a crucial role in ensuring that only legitimate clients can interact with the API, providing a basic level of security. When a developer registers an application with an API provider, they receive an API key, which must be included in all API requests. This process allows the API provider to monitor usage, enforce rate limits, and manage access to different API functionalities. API keys are commonly used in various web services, cloud applications, and third-party integrations. They offer a straightforward way to control and track API usage. However, it's essential to keep API keys secure, as exposure can lead to unauthorized access and potential misuse. Developers should avoid hardcoding keys in publicly accessible code repositories and consider using environment variables or secure vaults for storage. Additionally, implementing additional security measures, such as OAuth, can further enhance protection.

Take a look at out top 10 best serverless platforms. Each of them offers different features and integrations so that you can find the solution that suits you best. Read more about them in our latest article! #top10 #serverless #platform

Ever feel like you're drowning in duplicated code across your microservices? 😩 You're not alone!  Let's say authentication for example – hardcoded credentials, custom logic in each service – it becomes a nightmare to manage as your app scales. But what if there was a way to centralize authentication, simplify policy updates, and free your applications from this burden? 🤔 Imagine you have an application with multiple services, each with its own basic authentication setup. Keeping track of credentials and managing changes becomes a tedious task. A single WasmPlugin can revolutionize this! 🌟 This plugin, would live outside your applications, handling authentication centrally. (See the slides) With this approach, your applications no longer need to worry about the specifics of basic auth or manage credentials. They simply call the Istio service, and the WasmPlugin seamlessly verifies authorization. This brings a wave of benefits: 1️⃣ Centralized Management: Update authentication policies from a single place, no need to touch individual applications. 2️⃣ Enhanced Security: Credentials are removed from applications, reducing the attack surface. 3️⃣ Future-Proof Flexibility: Need to switch to JWT or OAuth? Simply update the WasmPlugin, not your applications! Has traditional in-app authentication got you down? Let's discuss how WasmPlugins can streamline your deployments! Want to see more posts like this? Follow #istio_tutorial for an upcoming series on Istio! --- Are you interested in #cloudnative projects such #kubernetes and #istio like me? Click my name + follow + 🔔 so you don’t miss out!

Building cloud-native .NET applications shouldn't be a battleground. Explore the two main contenders, .NET Aspire and Docker, to help you choose the champion for your next project. Find in the link below: 🎯 .NET Aspire: A streamlined approach for .NET developers, offering features like boilerplate code reduction and easy cloud service integration. 🎯 Docker: The industry standard containerization tool, ensuring portability and scalability for your applications. 🎯 The ultimate decision guide: We analyze the strengths and weaknesses of each tool to help you pick the one that best suits your project needs, from greenfield development to existing app modernization. Don't waste time and resources on the wrong tool. Read now and make an informed decision: https://lnkd.in/eRQpc5um #dotnet #docker #cloudnative

🚀 Attention, fellow developers! 🌟 Looking for amazing free resources to level up your skills and projects? 🎉 Check out Free for Dev. A treasure trove of free services & tools tailored for developers! 🛠️💻 From cloud hosting to development tools, there’s something for everyone. Don’t miss out on the chance to enhance your toolkit without breaking the bank! 💰✨ 👉 Dive into the list here: [Free for Dev](https://lnkd.in/ecMPECQZ) Let's build something amazing together! 💪 #DeveloperTools #FreeResources #CodingCommunity

For those of you looking for open source infrastructure, look no further, Smart Account, Marketplace, DRM, & NFT infrastructure all in one place. For the first time, 88+ documented API endpoints are available for enterprises to deploy via a novel open-source token licensing model.

OAuth 2.0 Explained Imagine you have a secret fort filled with cool gadgets and games (your data and online accounts). You wouldn't just hand out the key to everyone, right? OAuth 2.0 is like a special way for other websites and apps to access some of your stuff without needing the actual key. Here's how it works: The App Asks Permission (Authorization Server): An app you want to use (like a special game website) needs something from your fort (like your high score or username) stored somewhere else (on a website with your account information). This "somewhere else" is called the authorization server. You Give Permission (Resource Owner): You, the one in control of the fort (resource owner), get to decide! The game website asks you if it can borrow some information from your fort (like your username). Safe Sharing (Resource Server): If you say yes, you don't give the game website the key to your whole fort (your password). Instead, the authorization server gives the game website a special one-time code. This code lets the game website access the specific gadget it needs (your username) from your fort (resource server where your data is stored), but it can't open the entire fort and see everything else. Playing the Game: Now the game website can use your username to show you your high score, and you can both enjoy the game! Benefits of OAuth 2.0: Safer: You don't share your actual key (password) with other apps. Easier: No need to remember different passwords for different apps. Convenient: Apps can access the information they need without you needing to log in every time. Follow for more visual contents on DevOps and Cloud Computing #DevOps #CloudComputing #DoVisuals #OAuth2.0