ic_agile_128ic_business_128ic_agile_white_128ic_banknote_smile_128ic_business_128ic_business_128ic_checkmark_128ic_client_team_manager_128ic_code_file_128ic_code_files_128ic_corporate_cloud_platforms_128ic_crossplatform_apps_128ic_dedicated_team_128ic_developer_128ic_development_team_128ic_enterprise_128ic_faster_timeframe_128ic_fixed_price_128ic_graph_down_128ic_graph_down_128ic_hourly_128ic_hourly_white_128ic_information_finder_128ic_junior_developer_128ic_managed_team_128ic_message_128ic_mobile_app_startups_128ic_mobile_development_128ic_mobile_development_up_128ic_mobile_devices_128ic_multiplatform_128ic_multiplatform_white_128ic_pricetag_128ic_project_checklist_128ic_project_management_128ic_project_management_team_128ic_research_and_development_team_128ic_scalable_team_128ic_senior_developer_128ic_smaller_codebase_128ic_smaller_price_128ic_startup_128ic_team_manager_128ic_three_times_faster_128Arrow_Dropdownic_001_google+_16ic_002_xing_16Group 2ic_003_facebook_16ic_004_linkedIn_16Groupic_005_message_16ic_006_upload_16ic_007_remove_16ic_008_email_16ic_009_attachment_16ic_010_file_16ic_011_name_16ic_012_arrow_left_16ic_013_arrow_right_16ic_014_arrow_down_16ic_015_arrow_up_16ic_016_dropdown_arrow_down_16ic_016_dropdown_arrow_leftic_016_dropdown_arrow_rightic_017_K&C_dropdown_arrow_up_16ic_018_language_16ic_019_Quote_16ic_020_+_16ic_021_=_16ic_022_phone_16ic_023_twitter_16ic_024_position_16ic_025_company_16ic_026_search_16ic_027_mobile_16ic_028_fax_16ic_029_location_16ic_030_enlarge_16ic_031_downscale_16ic_032_contactic_download_normal_16pxic_033_skype_16ic_006_download_16 copySearchGroup 26Rss_font_awesomelinkedintwitterK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxK&C_Icons_32pxConsul_VerticalLogo_FullColorPacker_VerticalLogo_FullColorTerraform_VerticalLogo_FullColorVault_VerticalLogo_FullColorethereum_black_64ic_Interest_based_64ic_acrivate_card_64ic_api_client_64ic_application_architecture_64ic_application_architecture_ white_64ic_application_development_user_64ic_application_development_user_64ic_arrow_down_64ic_automated_backups_64ic_automated_infrastructure_provisioning_64ic_automated_infrastructure_provisioning_white_64ic_automated_storage_64ic_automated_storage_64ic_automation_64ic_microservice_architecture_64ic_avaliability_across_the_world_64ic_avaliability_across_the_world_white_64ic_blockchain_64ic_blockchain_white_64ic_brackets_64ic_brackets_64ic_build_64ic_build_64ic_build_64ic_business_64ic_business_partnership_64ic_business_partnership_white_64ic_business_64ic_calculator_64ic_calendar_64ic_calendar_64ic_car_rent_64ic_card_renewal_64ic_chat_64ic_chat_bubbles_64ic_chat_bubbles_64ic_chat_white_64ic_checklist_64ic_checkmark_64ic_blockchain_64ic_smart_development_64ic_blockchain_consulting_64ic_checkmark_white_64ic_clock_64ic_clock_white_64ic_cloud_media_64ic_cloud_solutionsic_cloud_solutions_whiteic_cluster_64ic_cluster_white_64ic_code_base_optimization_64ic_coding_64ic_coding_white_64ic_commenting_widget_64ic_commenting_widget_64ic_containers_64ic_containers_white_64ic_continious_64ic_continious_delivery_64ic_continious_delivery_white_64ic_continious_release_64ic_continious_release_white_64ic_continious_white_64ic_cost_saving_64ic_cost_saving_white_64ic_cpu_load_64ic_credit_card_64ic_crossplatform_app_development_64ic_crossplatform_app_development_white_64ic_custom_crm_64ic_custom_crm_64ic_independence_consulring_64ic_database_calls_64ic_database_calls_white_64ic_dedicated_teams_64ic_dedicated_teams_64ic_desktop_application_user_64ic_desktop_application_user_64ic_desktop_code_64ic_desktop_code_white_64ic_developer_64ic_developer_white_64ic_development_64ic_devops_64ic_devops_64ic_documents_64ic_documents_graph_64ic_documents_graph_white_64ic_documents_white_64ic_download_presentation_64ic_education_64ic_email_open_64ic_email_open_white_64ic_environment_healthcheckethereum_white_64ic_euro_64ic_euro_white_64ic_failure_solved_64ic_gdpr_64ic_globe_outlines_64ic_good_quality_64ic_high_load_websites_64ic_high_load_websites_white_64ic_hotel_booking_64ic_inability_64ic_inability_white_64ic_increase_64ic_increase_white_64ic_increasing_team_64ic_independence_64ic_integration_64ic_it_outsourcing_64ic_it_outsourcing_64ic_knowledge_sharing_64ic_mobile_devices_64ic_laptop_user_64ic_laptop_user_white_64ic_launch_64ic_launch_white_64ic_learning_64ic_learning_two_white_64ic_lighthouse_64ic_link_64ic_load_balancer_64ic_load_balancer_64ic_load_card_64ic_lock_64ic_lock_white_64ic_low_cost_64ic_low_load_websites_64ic_maintenance_tools_64ic_maintenance_tools_white_64ic_media_player_64ic_media_player_white_64ic_messaging_platforms_64ic_microservice_architecture_64ic_microservices_64ic_microservices_64ic_mobile_app_64ic_mobile_app_64ic_mobile_content_64ic_mobile_development_64ic_mobile_development_white_64ic_mobile_devices_64ic_mobile_devices_white_64ic_mobile_payments_64ic_mobile_social_media_applications_64ic_mobile_workflows_64ic_money_transfers_64ic_multimedia_sharing_64ic_multimedia_sharing_white_64ic_my_garage_64ic_no_access_64ic_no_access_white_64ic_no_oldschool_64ic_online_marketplaces_64ic_online_marketplaces_white_64ic_online_trading_64ic_online_trading_64ic_pair_device_64ic_parallels_64ic_parallels_white_64ic_passcode_64ic_payment_systems_64ic_performance_64ic_performance_issues_64ic_performance_issues_white_64ic_performance_white_64ic_plane_64ic_plane_white_64ic_plus_64ic_plus_64ic_pricetags_64ic_pricetags_64ic_product_64ic_product_search_64ic_product_white_64ic_productivity_tools_64ic_productivity_tools_64ic_project_delivery_64ic_project_delivery_white_64ic_project_management_64ic_project_management_collaboration_64ic_project_management_team_64ic_project_management_team_white_64ic_project_risks_reduced_64ic_quality_mark_64ic_quality_mark_64ic_quality_mark_white_64ic_question_64ic_react_native_64ic_response_time_64ic_response_time_white_64ic_rest_api_64ic_retail_64ic_transparency_consulting_64ic_scale_up_64ic_scale_up_white_64ic_security_64ic_security_64ic_self_healing_64ic_self_healing_64 copyic_send_money_64ic_server_64ic_server_white_64ic_shopping_64ic_shopping_white_64ic_sleep_mode_64ic_small_is_beautiful_64ic_smaller_price_64ic_social_benefits_64ic_social_connections_64ic_socket_64Group 20ic_spare_parts_for_cars_64ic_spare_parts_for_cars_white_64ic_speedometer_64ic_performance_consulting_64ic_speedometer_white_64ic_startup_64ic_startup_white _64ic_target_64ic_team_64ic_testing_64ic_testing_checklist_64ic_testing_checklist_white_64ic_testing_white_64ic_three_times_faster_64ic_touch_64ic_touch_id_64ic_touch_white_64ic_transparency_64ic_ui_design_desktop_64ic_ui_design_mobile_64ic_ui_design_mobile_white_64ic_umbrella_64ic_umbrella_64ic_umbrella_white_64ic_up_and_down_scaling_64ic_up_and_down_scaling_64ic_users_64ic_users_white_64ic_ux_design_64ic_ux_design_desktop_64ic_ux_design_64ic_ux_design_white_64ic_vehicle_64ic_web_based_search_64ic_web_based_search_white_64ic_web_browser_code_64ic_web_browser_developer_mode_64ic_web_browser_user_64ic_web_development_64ic_web_development_white_64ic_web_portals_64ic_web_portals_64ic_web_user_64ic_web_user_white64ic_workflow_64ic_workflow_steps_64ic_workflow_steps_white_64ic_workflow_white_64ic_working_environment_64solidity_blackGroup 19

Pros and Cons of Serverless Web Development

We Love The Potential Of Serverless Development But It’s Not a Miracle Cure

In our previous article on serverless web development we discussed why at Krusche & Company we believe serverless to be the future of web development. The focus was undeniably on the strengths of serverless architecture. In this instalment of our Serverless architecture consulting series, we’ll add more balance to the picture by also outlining serverless cons.

 

Of course, no technology or architecture is the perfect solution across every business and engineering consideration it influences. However, what is important is whether a tech stack’s combined strengths minus weaknesses equal a superior consensus solution compared to alternatives. Can perceived weaknesses in serverless web development be bridged in a way that means they do not drag on the technology solution or business case to the extent the strengths are compromised?

 

We’ll also apply the theory of serverless web development’s pros and cons to example applications. This will illustrate the conditions under which the balance of serverless’s pros and cons make it a great choice of tech stack and those where it probably isn’t the optimal choice.

 

In the interest of balancing out the slightly gushing pro-serverless position in our previous article, let’s kick off with drawbacks to serverless web development this time around:

Serverless Web Development Cons

So, which are the possible concerns and drawbacks to taking a serverless development approach?

    

Vendor Lock-in

Discussions with our own architects and clients around whether serverless is the right way to go with a new development project often sees concerns raised around vendor lock-in. There is the perception that once the serverless architecture of an application is set up with one Cloud vendor (GCD, AWS and Azure being the usual options) it’s very difficult (expensive and time consuming) to then migrate to another if circumstances change.

 

In reality, and given the right approach from a new application project’s outset, vendor lock-in doesn’t need to be a serverless development drawback. At least, not for most applications. Migration between vendors can be unavoidably complicated for really big applications.

 

For example, you are designing a web application with the following functionality:

 

·        Secure user identification

·        Collection and storage of some personal data

·        A user interface to app functionalities 

 

Let’s compare the tech stacks a traditional web development or serverless development approach would require.

Traditional web development:

 

    - Identification: Spring Security Framework (Java)

    - Data storage: NoSQL better fits here as no transactions are required (MongoDB)

    - Notifications: Spring with Websockets

    - Payment: 3rd party service

    - Business logic core: Spring Framework (Java) with REST Endpoints

 

Serverless web development with AWS:

 

    - Identification: AWS Cognito

    - Data storage: AWS DynamoDB

    - Notifications: AWS Simple Notification Service

    - Payment: 3rd party service

    - Business logic core: AWS Lambda

   

Many different applications include the need for user identification, data storage, notifications and payments. Beyond that, only the ‘core’ of the application, will be something that could be considered ‘unique’.

 

Traditional web develop necessitates custom configuration and coding of user identification, data storage, notifications and payments. So any changes made to improve, evolve or fix problems in the app necessitate a new software development iteration cycle. This means any changes are resource (time and money) intense.

 

Serverless web development, on the other hand, allows you to use ‘plug-and-play’ technologies for the common functionalities the app involves – user identification, payments etc. The AWS tools listed above (Cognito, DynamoDB etc.) just need to be configured and can then quickly and easily be changed between test and production environments.


This means serverless development should save a lot of time and money both in the initial development stage and when any subsequent changes or updates need to be introduced. 

But how does the above relate to ‘vendor lock-in’ concerns around serverless development? Let’s say you want to move your application from AWS to Google Cloud. Several AWS technologies have been used in your application. Which was great while using the AWS Cloud. But it’s going to be a problem now, right? Yes. Switching them out for Google Cloud equivalents will be a pain. Which is the crux of the vendor lock-in criticism of serverless development.

 

But that doesn’t need to be the case. If the Serverless Framework is adopted from the get-go, a serverless application can be built as ‘Cloud-vendor agnostic’. The serverless framework solution allows you to set up your serverless architecture with one common configuration file in which you will only need to change the name of the Cloud vendor to switch out AWS technologies for Google Cloud (or those of any other major vendor) equivalents. Nothing else needs to be touched and your app will work exactly as before in its new Cloud home.

 

Serverless development done right should mean migrating between Cloud vendors is as easy as changing mobile operators while retaining your old number has become in recent years. The framework that supports serverless development is maturing quickly and obvious weaknesses such as vendor lock-in are being addressed. Businesses are increasingly convinced that major cons to the serverless tech stack are being neutralised, leaving its strengths uncompromised.

 

Patrick Brandt, Solution Architect at the Coca Cola Company recently stated:

 

“The Serverless Framework is a core component of The Coca-Cola Company’s initiative to reduce IT operations costs and deploy services faster”.

 

Too positive? Are we skating over drawbacks to serverless? From my point of view there is only one thing that could mean vendor lock-in is a concern that could dissuade you from adopting serverless development for your next project – the components you NEED to use for common functionalities require unique code full control over is non-negotiable. 

Pros and Cons of Serverless Web Development

Are Serverless Running Costs A Con?

Another argument often used in opposition to a Serverless development approach to new applications is potential computing costs. I’ve heard a number of times that Cloud resources can be expensive and the user has no control over costs.

 

That is partially true. Traditional development does mean computing resource overheads can be accurately forecast. A business knows exactly how many servers will be needed for an application, where they’ll be located etc. Budgeting is easy.

 

If you opt for a Cloud Serverless environment, you receive the bill at the end of the month and it can be difficult to predict the exact cost. A sting in the tail is possible. This lack of control over overheads is often what discourages companies from investing in Serverless technology.

 

From a business perspective, not being able to accurately control or predict costs is a deal-breaker. Could that be the bottleneck that means the future for Serverless development will fail to match current hype?

 

I don’t think so. Firstly, accurately predicting Cloud resource costs for serverless applications really isn’t that difficult if you know what you are doing. You only need to define exactly what Cloud resources your app will used and how these fit into a vendor’s pricing structure. Yes, you may not be able to accurately predict demand for your application and usage levels. If it goes viral will you be bit with a Cloud vendor invoice that could kill your company?


It is a consideration but not one that, in the vast majority of cases, will really influence if Serverless is the appropriate technology. In fact, start-ups ofter favour Serverless exactly because costs are back loaded. Running an app is very cheap until it has a large number of users, at which point additional costs should be justifiable. This also makes Serverless an ideal architecture for MVPs and new products.

Firstly, if an application is one that monetises directly, revenues should scale with Cloud resource costs if demand spikes. If an application doesn’t monetise directly, presumably it adds another kind of business value that will indirectly represent financial gain for the company.


There may be scenarios where unexpectedly high Cloud resource costs could negatively impact a business’s cash flow despite positives of higher than anticipated demand for an application. But it should be clear from the outset if there is any chance of such a scenario unfolding. There may be other solutions than simply rejecting Serverless and its strengths as a technology stack.

 

In the majority of scenarios, an application maintaining consistent performance during demand peaks will be the overriding business consideration. Have you ever left a portal because it’s slow or has crashed during periods of peak use? I did exactly that last week when buying a gift for a relative.

 

Three e-markets offering the same product at the same price. Two were significantly slower than the third (2-4 seconds slower filtering). Yes, perhaps the slower applications were just the result of inferior build. But if they have the same code how efficiently can they can scale to meet demand?

 

If you’re hard wiring server capacity, how do you know what resources peak demand might require? The chances are your servers will rarely be close to optimal capacity. They’ll either offer too much capacity, that you’ve paid for and is sitting idle 90% of the time or not enough at peak moments, either slowing down or crashing, losing your business.

 

With Serveless, you don’t need to ‘hard plan’ capacity. It will scale seamlessly to meet demand. There are many ways you might lose business but server capacity running at the level you need it to be is not one of them.

   

Serverless is a particularly good fit if you don’t really know what demand might be put on an application. You will only pay for what you use, allowing you to feel things out.  That doesn’t mean cost planning isn’t important in Serverless. Components costing should be diligently researched and technology optimised for data query planning, lambda memory and time consumption planning.

 

In conclusion, if your application is mature and demand trends and server capacity requirements accurately predictable for the long term, Serverless may not be the cheapest option available to you. Opting for your own fixed server resource might make sense. But even in this scenario, a hybrid Cloud solution able to scale with any unexpected peaks in demand is still worth considering. 

Complicated Integration/Migration From Current Non-Serverless Solution

I agree that migrating existing architecture to a Serverless architecture or hybrid solution can represent a challenging epic. However, the crux of the problem tends to be, in my experience, reliance on developers that lack the relevant expertise. Transitioning an organisation to the Cloud requires investment in new skills. That might mean training being provided for in-house development professionals or bringing in experienced outside help.

 

One of the fundamental differences between Serverless development and traditional development is that Serverless developers need to consider and be able to accurately calculate the costs associated with how they have built an application. How much will the technology components used, database requests, computing time and performance cost? Are those costs compatible with the application’s business case and plan? Traditional web developers don’t have to worry about these questions. It’s not their job.

 

For me personally, as a developer who has transitioned from traditional to Serverless development, this was one of the most difficult evolutions in the nature of the job to get to grips with. An organisational transition to Serverless, either entirely or for certain applications, should take this into consideration. Developers need to be re-educated that their job now involves managing an application’s running costs within the context of its business case. 

When Is Serverless Development The Optimal Choice For An Application?

Let’s sum up the business considerations and technical qualities of an application that broadly speaking mean it would generally benefit from going Serverless:

 

    - small to middle-size applications

    - not yet established market with unpredictable load

    - application requires a lot of quick (fail-fast) experimenting

    - no unique proposition in common modules (identification, notification)

    - team is prepared to leverage Serverless advantages

 

When Serverless is probably not the optimal technology stack for an application:

 

    - large applications

    - established and predictable market demand and peak load times

    - application is featured iteratively and slowly - experiments aren’t welcome

    - fine grained control is needed in common modules and they contain unique flows

    - team is not prepared and hasn’t adopted Cloud Serverless thinking

  

In our next article on Serverless development, we’ll outline the strengths and benefits of the common ‘plug and play’ components offered by AWS.

Krusche & Company – Serverless Development Consulting

Munich-based Krusche & Company has established itself as one Germany’s most trusted development and IT consulting firms over our over 20 years of operations. Specialised in DevOps and Cloud transformation and development, we provide consultants, dedicated teams and team extensions. Our extensive list of partners ranges from some of Europe’s best known brands to high-performing SMEs and exciting start-ups.

 

If you are considering a Serverless approach to your next project or a wider DevOps, Cloud or Serverless organisational transition, please do not hesitate to get in touch. We’d love to hear from you. 

SHARE WITH FRIENDS
You might find this interesting
E-book
Hiring Web Developers — The Complete Guide
E-book
Top Tools for Cost-Effective Web Development — eBook
Our cases
Reformation of Deployment Cycle for Bosch Classic Cars Portal
Our cases
Fast and Lightweight Mobile Application based on PhoneGap/ Cordova
E-book
Determining Approaches to Mobile App Development
Our cases
VAIX - Fault tolerant infrastructure for 24/7 high-load machine learning service
Testing
Fallstudie Testautomatisierung: Cucumber, Selenium und Jira Xray
Web,Amazon Web Services
Vorteile durch Serverless Development für Startups: niedrigere Kosten, kürzere Time-to-Market
Other
ANGULAR, VUE, JQUERY, REACT ODER EMBER?
DevOps
Kubernetes Beratung – Übernehmen Sie die Kontrolle über Ihre K8s!
DevOps
Ist serverlose Architektur die Zukunft der Webentwicklung?
Testing
Qualität + Transparenz durch Agile Test Coaches
DevOps
KUBERNETES-BERATUNG: SCHRITT FÜR SCHRITT ZUM HEPTIO ARK (VELERO) BACKUP
Our cases
Bosch Classic Cars - Digital Engagement Platform for 19K Vintage Car Owners
Our cases
Drivelog.de — Web Marketplace for Car Owners and Service Providers
Our cases
Portal Performance Tuning For Major German Travel Agency
Our cases
The Platform Providing Event Organization
Our cases
Reference: Major producer of auto electronics and spare parts
Our cases
Liferay Portal Developers: Performance Tuning Case Study
Our cases
How to apply React Native while developing heavy cross-platform mobile apps
Web,Mobile,Amazon Web Services
SERVERLOSE ARCHITEKTUR FÜR CLOUD-BASIERTE APPS: TECHNOLOGIE-ANBIETER UND GRENZEN
Outsourcing
Agile entwickeln mit festen Budgets | K&C Software München
Our cases
Micro-service Architecture for New AngularJS Application - Case Study
DevOps
Cloud-Trends 2019 - Hybrid, SAAS und PAAS | K&C Beratung
Other
Swimming with Sharks
Web
Serverless Application Developers: Our Tech Talent, Your Success
Web,Amazon Web Services
React Developers Munich
Amazon Web Services
Hybrid Cloud Consulting Services in Munich
Other
Don’t Treat Me Like a Fool: The worst thing you can do for your business
Web
Technologies that Foster Digital Transformation
Web,Other
How to Make Your Web Solution Rock: 7 Areas to Check
Web
K&C insights: how to make your workflow work for you
Web
Advanced Technologies for Marketing Automation
Other
I’m Tired of Blockchain Hype, Are You?
Outsourcing
SCALED AGILE FRAMEWORKS: HINTERGRÜNDE UND AUSFÜHRLICHER LEITFADEN
DevOps,Outsourcing
AWS DevOps: A New Way to Run Business
Web,Outsourcing,Other
Angular 5.0.0 – A Better Version of Itself
Other
Culture eats technology for breakfast
Web
When Microservices Help Make Future-Ready Products
Web
Plan to Succeed: 4 Tips for Building Scalable Software
DevOps
Hybrid, SAAS+PAAS: cloud solution trends to watch in 2019
Web
4 Time-Saving Ways to Test Your Cross Platform Mobile App
DevOps
Serverless Architecture Consulting Services
DevOps
DevOps als DevSecOps – Integrierter Schutz vor Bedrohungen ohne Termin- und Budgetüberschreitung
Web,Outsourcing,Other
JavaScript & WebSockets: How to Build Real-Time Applications
Web,Amazon Web Services
Your Expert Angular Developers in Munich | K&C Development
Web
A secret formula of an agile dream team
Our cases
CLOUD-LÖSUNG VS. BARE METAL SERVER: WANN MACHT WELCHER ANSATZ SINN?
Web,Outsourcing
Angular 6 Will Be A Hit
E-book
Digital Transformation: the Philosopher’s Stone of Economic Growth
Web,Outsourcing,Testing
Sicherheit für Web-Anwendungen - dank Threat Modeling
DevOps
How to start services on Linux
DevOps
How We Manage Our Infrastructure with Chef
Web
Cost efficient technologies
Web
Fintech Apps - A Lucrative Solution for Customers and Businesses Alike
Other
Europe’s Big Payments Directive PSD2
Outsourcing,Testing
Die Rolle des QS-Teams in Software-Projekten
Web,Outsourcing,Other
Angular vs. React vs. Vue – Let the Fight Start!
Web,Mobile,Outsourcing,Other
All You Wanted to Know About Chatbot Platforms
DevOps
How to setup Kubernetes cluster on AWS
Web
Centralized Logging with Logstash, Elasticsearch & Kibana
Our cases,Amazon Web Services
CLOUD SOLUTION VS. BARE METAL SERVER: WHEN AND WHY
Web
Why Serverless Development For Start-Ups: Lower Costs, Faster to Market
DevOps
How to Build a Rancher & Docker Based Cloud
DevOps
Setting Up: Traefik Balancer In Rancher Cloud
Web,Amazon Web Services
Serverless vs. Hadoop & Containers In The Evolution Of Big Data & AI
Web
Agile and DevOps are Key Drivers of Digital Transformation
Web,Amazon Web Services
What's New In React 16.3.0 - 16.4.2 | K&C React Dev
Web,Other
JAMSTACK IS THE NEW FACE OF STATIC SITES
Web
A Guidance for Keeping Your Web Development Project Within the Budget: Three Key Pillars
Web,Outsourcing
Migration from Angular 1 to Angular 5
Web,Outsourcing,Other
Golang vs. Node.js
Amazon Web Services
Auswahl Cloud-Provider ohne Vendor Lockin
Web,Outsourcing,Other
How a Company Can Benefit from White Label: K&C experience
Web,Outsourcing,Other
Angular 5 VS React.js – Who’s Going to Set the Tone in the Upcoming Year?
Other
Big Data: Why Your Business Needs it ASAP
Web,Our cases
White Label: A Customized Software Solution from a Business and Tech Perspective
Web,DevOps,Our cases
Our case: Marketplace for gaming goods
Web,Outsourcing,Testing
Web App Security 101: Keep Calm and Do Threat Modeling
Web,Outsourcing,Other
JS Frameworks: The Trendiest Frameworks You Should Know
DevOps
Docker: Virtualize Your Development Environment Right
DevOps
DevOps with Puppet: Tips on Setting it up for Configuring Servers
Web,Mobile
Wann eignen sich Progressive Web Apps ?
Web
Angular 2.0 vs Angular 1.4. What fits you best?
Web,Amazon Web Services
CLOUD DEPLOYMENT: YOUR APPLICATION’S OPTIONS
Outsourcing
SCALED AGILE FRAMEWORKS: YOUR COMPLETE GUIDE TO WHICH, WHY AND HOW
DevOps
Installation and setting up: Nextcloud as a local network storage on CentOS7
DevOps,Outsourcing
KUBERNETES ALS FÜHRENDE MICROSERVICE-ARCHITEKTUR IN PUNCTO SICHERHEIT
Testing
Agile Test Coach - Ensuring Code Quality & Transparency
Web
Debunking imaginary shortcomings of cross-platform frameworks
DevOps
Your DevOps Transformation Consulting Partner
Web,Outsourcing
How to Control Agile Development: Progress and Costs
Web,Amazon Web Services
Vue.js 2019 - not Angular / React
Other
The Power of the Holistic Business Analysis
DevOps,Outsourcing,Amazon Web Services
Information Security with AWS DevOps
Web
JQuery vs. Angular: Ad Astra per Aspera
DevOps
Kubernetes Consulting – Take Control of Your K8s!
Web,Outsourcing
Node.js vs. Angular.js – Two Sides of the Same Coin
Web
How to Motivate Your Dedicated Team to Work with Legacy Projects
Outsourcing
The BPM in the Microservice Environment
Other
GDPR: Smart Practices
DevOps,Outsourcing
Rancher 2.0: A Quick Look at the New Version
Web,Other
Dedicated Teams for Web Development: Choice Criteria to be Checked
Web,Amazon Web Services
Cloud App Security: Three Authentication Approaches
Web
Angular 4 vs React – what to choose in 2017
Web
Scaling software solutions - how it works
DevOps,Amazon Web Services
Kubernetes at the Forefront of Secure Microservices Future
Other,Marketing
How to Become a Leader in Your Market
DevOps
How We Use Ansіble for Configuration of Our Environments
Other
How to Convert Your Business to an Amazon-Style Market Leader
DevOps
Monolith, Microservices, Serverless... Which Will You Choose and Why?
Web
Microservices… when do we need them?
Mobile
Native or Hybrid Apps: A Quick Comparison
Web,Mobile,Back-end,Amazon Web Services
Why Enterprises Choose Serverless Architecture
Testing
What Is Quality Assurance and Why You Need It Immediately
DevOps
What to Choose: NFS or CEPH?
Web,Outsourcing
ANGULAR 6 versus REACT 16.3
Web
Web App Security 101: How to Defend Against a Brute Force Attack
Web,Other
GoLang: Features, Pros and Cons
DevOps,Outsourcing,Other
ROCKET.CHAT as an internal messaging system and helpdesk platform
Web,Mobile,Outsourcing
Progressive Web Apps and Why You May Need Them
DevOps
How To Launch Kubernetes Federation on Google Cloud Platform
DevOps
DevOps As DevSecOps – Full Integration of Threat Protection Without Compromising Deadlines or Budgets
Web,Amazon Web Services
ANGULAR 7 OR REACT For Your App?
Testing
Test Automation Case Study: Cucumber, Selenium and Jira Xray
Marketing
Аudience-based Marketing
Web,Outsourcing,Testing
QA for CxOs: How to Hire and Outsource
Web,Outsourcing
Angular 6 vs. Ember 3
Web,Amazon Web Services
Your Guide To AWS Cognito For Serverless User Authentication
Outsourcing,Other
How to Ramp up Your Team Wisely
DevOps
Security in Kubernetes and How Your Company Can Benefit from It
Web
All You Need to Know About Web App Security Now
DevOps
Serverless Providers: A Comparative Analysis of AWS Lambda, Azure Functions & Google Cloud Functions
Web,Amazon Web Services
Single Page Application SEO: Tips & Tricks
Other
Angular vs. Vue vs. jQuery vs. React vs. Ember
Mobile
WHY THE IONIC FRAMEWORK IS THE BEST CHOICE FOR YOUR HYBRID APP
DevOps
Guide for Hashicorp Consul/Vault with Kubernetes
Web,Other
SSR or CSR for Progressive Web App
Web
Node.js 10.0.0: Everyone’s Favorite Got Even Better
DevOps
DevOps Consulting – Our Business Is Automating Yours
DevOps
Is Serverless Architecture the Future of Web Development?
Outsourcing,Testing
How the QA Team Tests Your Project
Web,Mobile,Back-end,Amazon Web Services
Serverless Architecture for Modern Apps: Stacks Providers & Caveats
DevOps
Use case: how to build and run Docker containers with NVIDIA GPUs
Outsourcing,Amazon Web Services
FUNKTIONEN VON AWS LAMBDA DEBUGGEN
DevOps
Kubernetes backup with Heptio Ark (Velero)
DevOps
DEBUGGING AWS LAMBDA FUNCTIONS
DevOps
Kubernetes-Cluster absichern mit Hashicorp Consul/Vault